Systems, Devices and Methods for Vehicles

ABSTRACT

A system controls use of a mobile device in a vehicle where the mobile device includes, a hands-on user interface and a wireless communication interface. The system includes a docking station that couples to the mobile device using a hardwired connection, and a controller that couples to the docking station and a vehicle-start system. The hands-on interface is inaccessible with the mobile device received in the docking station. The system allows operation of the vehicle with the mobile device coupled to the docking station via the hardwired connection and prevents a vehicle start when the mobile device is not coupled to the docking station. The wireless communication interface is operational with the mobile device coupled to the docking station via the hardwired connection, and the controller permits, once the vehicle is started, a continued operation of the vehicle following removal of the mobile device from the docking station.

RELATED APPLICATIONS

This application claims priority to, and the benefit of each of, U.S.Provisional Application No. 61/569,585 filed on Dec. 12, 2011 and U.S.Provisional Application No. 61/653,438 filed on May 31, 2012. The entiredisclosure of each of these related applications is hereby incorporatedherein by reference for all purposes.

TECHNOLOGICAL FIELD

This application is related to systems, devices and methods forvehicles. In particular, certain embodiments described herein aredirected to safety devices, systems and methods for use with a vehicleand one or more mobile devices.

BACKGROUND

Driver distraction has become an increasing problem as mobile-device usehas become more common. For example, the ability of a driver to sendtext messages while driving leads to increased driver distraction,reduced reaction times and higher incidences of accident. This is trueof all drivers and particularly true of less experienced drivers. Manystates have attempted to deter distracted driving by making it illegalto: text while driving, perform any hands-on operation (calling ortexting) while driving or banning all such operation. While the lawshave been passed, such use is often a secondary offense in most statesor is not followed by most vehicle operators. Employers, for example,mass transit employers and fleet operators have also bannedmobile-device use (phones, tablets, etc.) while operating the masstransit or fleet vehicles.

Various approaches have been suggested to reduce the frequency ofdistracted driving. These include requiring that a mobile phone belocked within a container before the vehicle can be operated, disablingall mobile phones within a vehicle while the vehicle is operating andusing mobile-phone proximity sensing to confirm a location of the mobilephone near a seat belt or head rest of a vehicle.

Each of the preceding approaches suffers from one or more significantdrawbacks. For example, the effectiveness of each of these approachescan be compromised relatively easily by a motivated vehicle-operator.

SUMMARY

As used herein, the term “hardwired” refers to a physical connectionbetween two or more conductive elements in an electrical and/orelectronic system, for example, a connection provided when a firstelectrical connector is plugged into a second electrical connector. Aswill be apparent to one of ordinary skill in the art view of thedisclosure herein, the term “hardwired connection” can refer to apermanent physical connection or a temporary physical connection.Further, a hardwired connection can be completed via the contact surfaceor other conductor that need not include a wire. As used herein, theterm “coupler” refers to a connection between two or more elements wherethe connection may be completed using a hardwired connection, oralternatively, a wireless connection.

As used herein, the term “case” refers to a first element that receivesand at least partially encloses a second element of the system.Accordingly, as will be recognized by those of ordinary skill in theart, a case can include any of a jacket, a sleeve or other enclosure.Further, in some embodiments, with the second element (for example, amobile phone) received by the case, the two elements can be movedtogether in a conventional fashion for the mobile device while themobile device remains securely attached to the case.

As used herein, the term “annunciator” refers to an indicator that canbe detected by one or more human sense. For example, an annunciator caninclude an audible or visual indication observable to the human.Further, an annunciator can also include a buzzing or vibratory outputthat is detectable by human. For example in one embodiment theannunciation described herein is implemented via a vibratory output in asteering wheel or vehicle seat. As should be apparent to those of skillin the art in view of the disclosure herein, an annunciator can includeany of the preceding alone or in combination with one another or otherdetectable indicators.

As used herein, the term “flashing” refers to an act of reprogramming arewritable memory element without removing the memory element from thesystem. Accordingly, embodiments herein describe that vehicles includingan electronic engine control unit (ECU) can be reprogrammed byreprogramming a rewritable memory element in the ECU to include variousaspects described herein.

As used herein, the term “docking station” refers to an element thatreceives a mobile device. Depending on the embodiment, a docking stationmay or may not require a hardwired electrical connection. In someembodiments, for example, a docking station must physically receive amobile device to allow operation of the vehicle but need not complete ahardwired electrical connection with the mobile device. In otherembodiments, the docking station physically receives the mobile deviceand also completes a hardwired electrical connection with the mobiledevice to allow operation the vehicle.

In some embodiments, a hands-on user interface included in the mobiledevice is inaccessible with the mobile device received by the dockingstation, for example, the docking station may partially enclose themobile device when it is received to prevent access to the hands-on userinterface. According to other embodiments, the docking station may fullyenclose the mobile device. In some embodiments, a faceplate or otherpanel is employed in the docking station to prevent access to thehands-on user interface with a docked mobile device and the mobiledevice is not enclosed when it is received by the docking station.According to the some embodiments, the docking station can provide apedestal in which the mobile device is placed.

As used herein with reference to a vehicle being operating or anoperating vehicle, such terms refer to, but are not limited to, avehicle having an engine utilizing and/or producing power in somemanner, e.g. a combustion engine, a diesel engine, an electric drive, abattery, a fuel-cell or some other source of fuel or motive force thatcan provide a primary and/or secondary source of power used to propelthe vehicle. Depending on the embodiment, a vehicle is inoperative wherethe motive force is incapable of being used to propel the vehicle, forexample, because a combustion engine is not firing, a vehicletransmission is in park or a starting circuit is open.

In an aspect, a system for a vehicle comprising a processor and acircuit electrically coupled to the processor and configured to receivean input from a mobile device, the circuit constructed and arranged toprevent operation of the vehicle when the mobile device is not coupledto the circuit and to allow operation of the vehicle when the mobiledevice is coupled to circuit is provided.

In an additional aspect, an inline switch configured to prevent startingof a vehicle when a mobile device is uncoupled and to permit starting ofa vehicle when a mobile device is coupled is provided. In someembodiments, the inline switch can be configured to permit starting ofthe vehicle but may prevent shifting into drive (or reverse) until themobile device is coupled to the inline switch. As described herein, theinline switch can be positioned in, or electrically coupled to, manydifferent systems, e.g., may be configured as an inline switch that iselectrically coupled to and between the ignition system and the startersystem of the vehicle.

In an aspect, a docking station configured to couple to a mobile deviceis provided. In certain examples, the docking station can be configuredto couple to send a suitable signal to permit starting of the vehicleand/or switching of the vehicle from park into drive or reverse once themobile device is coupled to the docking station. In some instances, thedocking station may be configured to send a signal, e.g., continuouslyor intermittently, to prevent starting of a vehicle (or shifting thevehicle into drive or reverse) when the mobile device is uncoupled andthe signal may be interrupted by coupling of the mobile device to thedocking station such that starting of the vehicle or shifting thevehicle into drive or reverse is permissible once the signal from thedocking station is interrupted. Additional configurations and uses of adocking station are described in more detail below.

In an additional aspect, a coupler configured to couple to a mobiledevice and provide a compatibility feature to permit coupling of themobile device to one or more of the devices described herein isprovided. For example, a coupler can be connected to a mobile device andused to permit coupling the mobile device to a system even if in itsnative state the mobile device does not include the appropriate coupler.Examples of suitable couplers are described herein and include, but arenot limited to, those that include a suitable coupler on one side tocouple to a mobile device and a suitable coupler on another side or endto couple to a device or system as described herein, e.g., an Apple®iPhone type coupler on one end or side and a mini USB coupler on theother side that couples to the vehicle, a docking station or otherdevice or system as described herein. In some embodiments, the couplerscan be integrated into a phone jacket such that the coupler is designedto couple to the vehicle system is accessible externally and in thephone jacket. Other configurations of couplers suitable for use tocouple a mobile device to a vehicle system are described in more detailbelow.

In an aspect, a method of preventing a vehicle operator from starting avehicle when a mobile device is uncoupled comprising coupling a mobiledevice to a vehicle through a phone jacket is provided. In someembodiments, the method can also include sending periodic signals fromthe mobile device to the vehicle to ensure the mobile device remainscoupled to the vehicle. In other embodiments, the method can includedisabling the screen of the mobile device when the phone jacket iscoupled to the vehicle. In some examples, the method can permit startingof the vehicle but prevent switching the vehicle into drive or reverseuntil the phone jacket with the mobile device is coupled.

In another aspect, a method of preventing a vehicle operator fromstarting a vehicle comprising interrupting an ignition signal if amobile device is uncoupled to a docking station is described. In someexamples, the docking station may be operative as a mechanical switchthat is configured to disrupt any signal from the ignition switch if amobile device is not coupled to the docking station. In someconfigurations, the method can permit starting of the vehicle butprevent switching the vehicle into drive or reverse until the mobiledevice is coupled to the docking station.

In other aspects, a system configured to be coupled to the dash of avehicle and comprising a coupler to permit insertion of a mobile deviceinto the system is provided. For example, the system can replace thefactory radio in a vehicle and may include a suitable slot or openingthat permits insertion of the mobile device into the system. In someexamples, the system may comprise a case, sleeve or jacket that firstcouples to the mobile device and the sleeve or jacket is then insertedinto the system. In this latter configuration, the case, sleeve orjacket may comprise a suitable internal coupler to couple to the mobiledevice and an external coupler to couple the case, sleeve or jacket tothe system when the case, sleeve or jacket is inserted into, orotherwise coupled to, the system. In some configurations, the case,sleeve or jacket can be configured such that the display of the mobiledevice is not substantially viewable once the case, sleeve or jacket iscoupled to the system. In other configurations, the case, sleeve orjacket can be configured to couple to the system such that the displayof the mobile device is facing downward once the case, sleeve or jacketis coupled to the system.

In an additional aspect, a system configured to use one or morebiometric features optionally in combination with a mobile device isprovided. For example, a fingerprint or other unique biological featureor, in the alternative, a user code, can be used to enable the systemand permit starting of the vehicle and/or shifting of the vehicletransmission from park, e.g., into drive or reverse.

In a further aspect, a system configured to control an operating stateof a vehicle is provided where the system includes a docking station anda controller. In some embodiments the docking station is configured toreceive a mobile device and coupled to the mobile device using ahardwired connection. In further embodiments, the controller isconfigured to couple to the docking station and the vehicle ignitionsystem, and further configured to allow operation of the vehicle withthe mobile device coupled to the docking station via the hardwiredconnection when information that uniquely identifies a mobile device isprovided by the mobile device to the controller. In still furtherembodiments, the mobile device includes a mobile phone and theinformation includes at least one of a SIM number, an IMEI number and aUSB serial number. In one embodiment the controller is configured toperiodically poll the mobile device for the information.

According to an embodiment, the system includes at least one relaycoupled to the controller, the controller configured to operate the atleast one relay to prevent the vehicle from starting if the mobiledevice is not received by the docking station. According to oneembodiment, the at least one relay includes a first relay, and the atleast one relay further includes a second relay coupled to thecontroller the controller configured to operate the second relatedinterrupting ignition system to shut down the vehicle following aremoval of the mobile device from the docking station while a vehicle isoperating.

According to one embodiment, the system also includes a user interfacecoupled to the controller, the user interface configured to provide forentry of information that allows temporary operation of the vehicle withthe mobile device removed from the docking station. In one embodimentthe information includes a one-time code.

According to a further embodiment, the system includes a mobile-devicecase that is sized and configured to securely fit within the dockingstation with a mobile device received within the case. In oneembodiment, the mobile-device case is a first mobile-device caseconfigured to receive a first mobile device having a first size definedby a first set of dimensions, and the system also includes a secondmobile device case configured to securely fit within the docking stationwith a second mobile device received within the case, the second mobiledevice having a second size defined by second set dimensions differentthan the first set of dimensions. In still a further embodiment thefirst mobile-device case is configured to receive a first mobile phoneemploying a first hardwired electrical connection and the second mobiledevice case is configured to receive a second mobile phone employing asecond hardwired electrical connection different than the firsthardwired electrical connection. According to one embodiment themobile-device case provides a USB connection to connect themobile-device case including the mobile device to the docking station.

In still another aspect, a method of preventing operation of the vehicleand mobile-device based activities that otherwise contribute todistracted operation of the vehicle are detected is provided. In someembodiments, the method includes an act of establishing an authorizedmobile device for a system configured to uniquely recognize theauthorized mobile device, where operation of the vehicle is permittedwhen the authorized mobile device is coupled by a hardwired connectionto a docking station included in the vehicle. In further embodiments,the method also includes an act of authenticating a mobile-device IDcommunicated from a mobile device coupled to the docking station todetermine whether the mobile device coupled to the docking station isthe authorized mobile device. In still further embodiments, if themobile-device ID indicates that the mobile device coupled to the dockingstation of an inoperative vehicle is the authorized mobile device, thenallowing the vehicle to start; and if the mobile-device ID indicatesthat the mobile device coupled to the docking station of the inoperativevehicle is not the authorized mobile device, then preventing the vehiclefrom starting.

According to one embodiment the method also includes determining whethera mobile device is received by the docking station using a sensingelement included in the docking station. In another embodiment themethod includes determining, subsequent to the starting the vehicle,whether the mobile device remains coupled to the docking station by thehardwired connection. According to one embodiment, the method includesgenerating an audible alarm in the vehicle subsequent to an uncouplingof the authorized mobile device from the docking station while thevehicle is operating. In a further embodiment, the vehicle is shut down,a predetermined amount of time subsequent to the generation of theaudible alarm, if the authorized mobile device remains a couple from thedocking station while the vehicle is operating. According to oneembodiment the vehicle and shut down by interrupting ignition circuit.In still another embodiment, the method also includes determining,subsequent to the starry the vehicle whether the mobile device remainscoupled to the docking station by monitoring a status of a USBconnection of the mobile device and the docking station

In still another embodiment, the method includes an act of receiving anID associated with the authorized mobile device from the mobile device.These embodiments can also include an act of comparing the ID associatedwith the authorized mobile device with the mobile-device ID communicatedfrom the mobile device coupled to the docking station. According tofurther embodiments, the ID associated with the authorized mobile deviceis included in a look-up table in the controller and the controllerretrieves the ID associated with the authorized mobile device from thelook-up table to perform the comparison.

In still further embodiments, the method includes an act of polling themobile device coupled to the docking station for an identificationnumber that uniquely identifies the mobile device to the system. In oneembodiment the mobile devices is polled for at least one of a SIMnumber, an IMEI number and a USB serial number. According to oneembodiment, the mobile device is continuously polled for theidentification information. In another embodiment, the mobile device isperiodically polled for the at least one of the SIM number, the IMEInumber and the USB serial number. According to some embodiments,identification information other than or in addition to numeric data isemployed to authenticate the mobile device. According to one embodiment,the identification information used to authenticate the mobile deviceincludes alpha numeric information. According to another embodiment, theidentification information used to authenticate the mobile device doesnot include any numeric information.

According to still a further aspect, a system is configured to controluse of a mobile device in a vehicle where the mobile device includes, ahands-on user interface and a wireless communication interface and thesystem includes: a docking station configured to receive the mobiledevice and to couple to the mobile device using a hardwired connection,where the hands-on interface is inaccessible with the mobile devicereceived in the docking station; and a controller configured to coupleto the docking station and a vehicle-start system, the controllerconfigured to allow operation of the vehicle with the mobile devicecoupled to the docking station via the hardwired connection and toprevent a vehicle start when the mobile device is not coupled to thedocking station via the hardwired connection. According to thisembodiment, the wireless communication interface is operational with themobile device coupled to the docking station via the hardwiredconnection, and the controller is configured to permit, once the vehicleis started, a continued operation of the vehicle following removal ofthe mobile device from the docking station.

In one embodiment, the controller is configured to allow the vehicle tobe started following receipt, from the mobile device via the hardwiredconnection, of information that uniquely identifies the mobile device.In a further embodiment, the mobile device includes a mobile phone, andthe information includes at least one of a SIM number, an IMEI numberand a USB serial number.

In a further embodiment, the system includes an annunciator coupled tothe controller where the controller configured to operate theannunciator to notify an operator of the vehicle when the mobile deviceis removed from the docking station with the vehicle operating.

According to a further aspect, a method of controlling use of a mobiledevice in a vehicle is provided where the vehicle includes a dockingstation configured to receive the mobile device and the mobile deviceincludes a hands-on interface and a wireless communication interface. Insome embodiments, the method includes acts of receiving the mobiledevice with the docking station via a hardwired connection, where thehands-on interface is inaccessible with the mobile device received bythe docking station; if the mobile device received by the dockingstation is an authorized mobile device: allowing the vehicle to start;and if the mobile device received by the docking station is anunauthorized mobile device; preventing the vehicle from starting;permitting use of the wireless communication interface unit when thevehicle is operational and with the mobile device received by thedocking station; and permitting, once the vehicle is started, acontinued operation of the vehicle following removal of the mobiledevice from the docking station.

According to one embodiment, the method includes authenticating amobile-device ID communicated from the mobile device to determinewhether the mobile device coupled to the docking station is theauthorized mobile device. According to a further embodiment, the methodincludes authenticating the mobile-device ID using a USB serial numberassociated with the mobile device.

According to another embodiment, the method includes saving a record ofa removal of the mobile device from the docking station with the vehicleoperating. In a further embodiment, the method includes preventing are-starting of the vehicle when the record identifies a previous removalof the mobile device from the docking station with the vehicleoperating. In still a further embodiment, the method includes permittingthe re-starting of the vehicle following entry of a code that permits atemporary operation of the vehicle.

These and other features and aspects are described in more detail below.

BRIEF DESCRIPTION OF THE FIGURES

Certain embodiments are described with reference to the figures inwhich:

FIG. 1A is a flow chart of a method of controlling a vehicle, inaccordance with certain examples;

FIG. 1B is another flow chart of a method of controlling a vehicle, inaccordance with certain examples;

FIG. 2 is a flow chart of a method for coupling a mobile device to avehicle, in accordance with certain examples;

FIG. 3 is another flow chart of a method for coupling a mobile device toa vehicle, in accordance with certain examples;

FIG. 4 is a flow chart showing verification of a mobile device coupledto a vehicle, in accordance with certain examples;

FIGS. 5A and 5B are schematics showing open and closed ignitioncircuits, in accordance with certain examples;

FIGS. 6A and 6B are schematics showing open and closed braking circuits,in accordance with certain examples;

FIGS. 7A and 7B are schematics showing an in-line module, in accordancewith certain examples;

FIGS. 8A-8E are illustrations of vehicles, in accordance with certainexamples;

FIG. 9 is a schematic of a navigation system, in accordance with certainexamples;

FIG. 10 is an illustration of a mobile device, in accordance withcertain examples;

FIG. 11 is an illustration of a dock, in accordance with certainexamples;

FIG. 12 is an illustration of a mobile device case configured as a phonecase, in accordance with certain examples;

FIG. 13 illustrates a system in accordance with some embodiments;

FIG. 14A illustrates a flow diagram of system operation in accordancewith some embodiments;

FIG. 14B illustrates a flow diagram of system operation in accordancewith some further embodiments;

FIG. 14C illustrates a flow diagram of a further operation of a systemin accordance with still further embodiments;

FIG. 15 illustrates a flow diagram of yet another operation of thesystem in accordance with some embodiments;

FIG. 16 illustrates a flow diagram of still another operation of thesystem in accordance with some embodiments; and

FIG. 17 illustrates a mobile-device docking system in accordance withsome embodiments;

FIG. 18 illustrates an exploded of the mobile-device docking system ofFIG. 17;

FIG. 19 illustrates an exploded view of a mobile-device case inaccordance with some embodiments;

FIG. 20 illustrates a system in accordance with a further embodiment;

FIG. 21 illustrates a process in accordance with one embodiment;

FIG. 22 illustrates an isometric view of a mobile-device docking systemin accordance with some embodiments;

FIG. 23A illustrates a plan view of the mobile-device docking systemillustrated in FIG. 22; and

FIG. 23B illustrates a cross sectional view of the mobile-device dockingsystem illustrated in FIG. 23A.

DETAILED DESCRIPTION

Certain embodiments of the devices described herein can be used withpassenger and commercial vehicles including automobiles, trucks, trains,buses, subways, airplanes or other devices that include a combustionengine, electric engine, fuel cell or other engine or device that canprovide power to one or more wheels or other mechanisms of propulsion,e.g., a jet turbine. The exact configuration of the technology describedherein can vary depending on the end-use application, and theconfiguration may desirably be different where the technology is used ina passenger vehicle as compared to using it in a commercial vehicle orpublic transit vehicle. Unless otherwise clear from the context of theusage, the term “public transit vehicle” is intended to encompass allvehicles designed to transport people including subways, buses,airplanes, taxis, or other above or below ground electric or combustionengine powered devices commonly encountered or used to travel from oneplace to another.

In certain embodiments, the devices, systems and methods describedherein can provide many advantages including preventing non hands freemobile device functions, e.g., text messaging, while driving, reducingdriver distraction, permitting hands free use of a mobile device andother desirable features such as mobile device charging. These and otheradvantages will be recognized by the person of ordinary skill in theart, given the benefit of this disclosure.

There are many drawbacks of existing systems used to increase vehiclesafety. Some systems include complex sensors to detect proximity of thephone near a seat belt or head rest of a vehicle. See, for example, US20100087137. Shielding of the phone signal can trick the sensors intothinking no phone is present. In addition, software means can beimplemented to bypass the sensor system. Also, a “dummy” phone can beused to trick the system into thinking it has deactivated the operator'scellular phone.

In certain examples, the technology described herein can be used todisable non hands free functions of a mobile device, e.g., disablesending of text messages from a mobile device, or otherwise prevent avehicle operator from using non hands free functions while operating thevehicle. In some examples, the entire mobile device can be renderedinoperative or unusable, e.g., by locking the keyboard, disabling thedevice, disabling the interface screen, etc., whereas in other exampleshands free phone functions may still work and the mobile device maystill be able to receive text messages. It may be desirable to disableaudible receipt notices such that a vehicle operator is not distractedwhen a text message arrives at the mobile device. In certainembodiments, the technology described herein can be used to disable thevisual interface of the mobile device such that a user is unable tointeract manually with the mobile device when it is coupled to thevehicle. These and other features and configurations are described inmore detail herein and additional features and configurations will berecognized by the person of ordinary skill in the art, given the benefitof this disclosure.

In some examples, the technology described herein may be used to preventstarting of a vehicle until the driver's mobile device is coupled to thevehicle. In other examples, a vehicle may be started without the mobiledevice coupled to the vehicle, but the vehicle may not be put into gear,e.g., switched into drive until the mobile device is coupled to thevehicle. In some examples, coupling of the mobile device may enable fuelto be provided to the engine, whereas in other examples, when a mobiledevice is not coupled, a fuel shut off can be implemented such that thevehicle may not be started. In certain embodiments described herein, themobile device can be coupled to the vehicle in a wired or wirelessmanner. Notwithstanding that there are numerous ways to couple themobile device to the vehicle, when coupled the mobile device desirablyis not operative to send text messages by the operator of the vehicleand may also not be operative to use other non hands free functionspresent on the mobile device. The mobile device may still receive textmessages, send and receive phone calls by Bluetooth® devices or otherwireless units and perform other passive operations not requiring anyinput from the operator of the vehicle. Such desirable features permit avehicle operator to receive messages and information while not beingdistracted by those messages and information during driving.

In some embodiments, the exact configuration of the mobile device canvary and illustrative examples of mobile devices include, but are notlimited to, cellular phones, smart phones, laptops, handheld computers,personal digital assistants, enterprise digital assistants, iPad®devices, Iphone® devices, mobile internet devices and other devices thatcan send and receive text messages, e-mail or other communications. Insome embodiments, the mobile device can be configured to download aprogram to the vehicle or flash or reflash the processor, e.g., enginecontrol unit of the vehicle, to include a method, software or a key toidentify the particular mobile device, whereas in other examples, themobile device couples to the vehicle but does not otherwise control thevehicle.

In certain examples, one embodiment of the overall function of thedevice is shown in FIG. 1A. An operator first enters a vehicle. Theoperator then couples the mobile device to the vehicle at a step 110.Coupling of the mobile device allows the operator to start the vehicleat a step 120. Another embodiment of the overall function of the deviceis shown in FIG. 1B. The operator enters the vehicle and then starts thevehicle at step 150. The operator's mobile device is then coupled to thevehicle at step 160. The vehicle may then be shifted into gear, e.g.,from park to drive, at step 170. In other examples, coupling of themobile device to the vehicle may enable fuel to be provided to theengine of the vehicle.

In certain examples, the vehicle may include suitable hardware orsoftware to verify whether or not the mobile device is coupled to thevehicle. For example, the vehicle may include a software program orimplement a method that verifies that the mobile device is coupled. Oneillustrative method is shown in FIG. 2. The method includes receiving aninput to start the vehicle at a step 210. As discussed elsewhere herein,such input may be turning of a ignition switch, pushing of a button orusing the mobile device itself as a “key” to start the vehicle. Once theinput to start the vehicle is received, the method would verify that themobile device is coupled at a step 220. If the mobile device is coupled,then the vehicle would start at a step 230. If the mobile device is notcoupled at a step 240, then the vehicle may display a message at a step250 inquiring whether the operator would like to override the system ata step 260 or otherwise notify the vehicle operator that the mobiledevice is not coupled. If the override system is implemented by theoperator, then the vehicle would start at a step 230. If the overridesystem is not implemented by the operator, then the system would loopback to step 210 (or steps 240 or 250 if desired) to wait for operatorinput.

In certain embodiments, the exact form of the input to start the vehiclemay vary. In certain instances, the input may be an operator turning anignition switch that is standard on many vehicles. In other examples,the operator may push or activate a button. In addition examples,combinations of an ignition switch and a button can be used. In someexamples, the mobile device itself may be operative as a key to startthe vehicle. For example, the mobile device may include a uniqueidentifier, e.g., a SIM card identifier or the like, which permits onlythe holder of the mobile device to operate the vehicle. Coupling of themobile device by itself would permit starting of the vehicle, e.g.,using a push button. As discussed elsewhere herein, the system caninclude one or more accounts, logs or lookup tables that can store theunique identifiers of authorized users. For example, an administratormay input the SIM card ID's of desired operators into the system suchthat only those operators would be able to start the vehicle. In otherembodiments, the mobile device can be configured to receive a code thatcan be added into the phone before the phone is coupled to the vehicleto permit operation of the vehicle if the appropriate code is entered.

In certain examples, there may be instances where it is desirable tomove or start the vehicle where the operator does not have a mobiledevice or an authorized mobile device. For example, the vehicle may needto be serviced, parked, towed or otherwise operated by a non-authorizeduser for some time. When such a situation arises, the override systemmay permit operation of the vehicle without coupling a mobile device tothe vehicle. The override system can be configured to permit operationof the vehicle for a configurable period selected by an administrator orfor a pre-determined period present in the system. An operator may entera code into a keypad, the navigation system or other vehicle interfacepresent to permit starting of the vehicle in the absence of a coupledmobile device or to permit placing the vehicle in neutral for towingpurposes. In some examples, the override system can be configured topermit operation of the vehicle at low speed or a speed no greater thana speed selected by an administrator, e.g., 10 mph, 5 mph or less, topermit movement by a dealer, a service department, valet or the like. Inother examples, the override system can be configured to permitplacement of the vehicle into neutral so that it can be towed. In yetother examples, the override system may permit full functioning of thevehicle. In some examples, the override system can be coupled to a tiltsensor such that it is automatically activated if the vehicle is tiltedbeyond a certain angle, e.g., when towing, to prevent damage to thevehicle's power train components. While the override system can beconfigured for activation through a keypad or the mobile device, it mayalso be coupled to a transmitter/receiver to receive a remote signalfrom a satellite or other mobile device. For example, if a vehicleoperator loses their mobile device, a remote user can send an overridesignal to the override system of the vehicle to permit its operation inthe absence of the mobile device. This feature is desirable, forexample, in the event of mobile device loss or malfunction. In someexamples, the override system can include a time-out feature such thatafter a selected number of incorrect entries, no new entries will bereceived by the override system for a pre-selected period, e.g., 1, 5 or10 minutes.

In other embodiments, the method may permit starting of the vehicle butthe vehicle may not be switched into gear prior to coupling of themobile device. Referring to FIG. 3, the method includes receiving aninput to change the gear from park at a step 310. If the mobile deviceis coupled at step 320, then the gear can be changed at a step 330 topermit driving of the vehicle. If the mobile device is not coupled (step340), then the system may display a message at a step 350 inquiringwhether or not the operator would like to override the system at a step360 or otherwise notify the vehicle operator that the mobile device isnot coupled. If the override system is implemented by the operator, thenthe vehicle would change gears at step 330. If the override system isnot implemented by the operator, then the system would loop back to step310 (or steps 340 or 350 if desired) to wait for operator input.

It will be recognized by the person of ordinary skill in the art, giventhe benefit of this disclosure, that other methods can be used toimplement the technology described herein. In particular, any methodthat can limit starting of the vehicle or movement of the vehicle untila mobile device is coupled may be used to implement the technologydescribed herein. Accessory devices or modules can be used to implementthe technology, and such modules may be dealer installed, installed by amechanic or installed by the vehicle owner.

In certain embodiments, either or both of the methods described inreference to FIGS. 2 and 3 can be used with existing sensors and devicesin vehicles. For example, the system may use weight sensors built intothe seat in combination with the coupling of the mobile device. If theweight sensor is activated, then the mobile device can desirably becoupled before starting the vehicle or switching the vehicle gears. Theseatbelt sensor can also be used in combination with the mobile device.For example, the system may be designed such that starting of thevehicle (or switching from park to drive) is not possible until both theoperator's seat belt is fastened and the mobile device is coupled.Additional sensors including brake sensors, speed sensors, GPS trackingsensors and the like may also be used in combination with coupling ofthe mobile device. For example, in some embodiments any of the brakesensors, speed sensors, GPS tracking sensors and the like are employingcombination with the coupling of the mobile device to ensure that thevehicle is safely operated. The sensors can work in combination with themobile device to upload or store information to the mobile deviceincluding, but not limited to, vehicle average speed, top speed, fuelmileage, etc.

In certain embodiments, the mobile device itself may be used as thevehicle's key. In some examples, the system can implement a method thatuses coupling of the mobile device in combination with entering of aunique identifier in an interface in the vehicle, e.g., a navigationsystem, keypad or the like. For example and referring to FIG. 4, anoperator can couple a mobile device to a vehicle at a step 410. Once themobile device is coupled, a unique identifier can be entered into aninterface at a step 420. If the identifier matches with one in thesystem, then the vehicle may be started at a step 430. Alternatively,the transmission can be placed into drive (or reverse) once the uniqueidentifier is entered (step not shown). If the unique identifier doesnot match the one in the system, the system can display a message atstep 440 inquiring whether the operator would like to override thesystem at step 450. If the system is overridden, then the vehicle willstart at a step 430. When the mobile device is not coupled, the systemcan display a message at step 460 inquiring whether the operator wouldlike to override the system at step 470. If the system is overridden,then the vehicle will start at a step 430. As described herein, themobile device may be used in a wired or a wireless manner as thevehicle's key.

It will be recognized by the person of ordinary skill in the art, giventhe benefit of this disclosure, that the methods described in referenceto FIGS. 2-4 are merely illustrative and certain steps may be omittedand other steps may be added. For example, the method may be implementedwithout the ability to override the system such that coupling of themobile device to the vehicle is required to start the vehicle or changethe gear of the vehicle.

In certain embodiments, when the mobile device is coupled to thevehicle, the mobile device may be rendered “dumb” such that texting orother features that require manual input are disabled. In someinstances, it may be desirable to disable all features of the mobiledevice, whereas in other examples, the device may be able to receiveincoming phone calls but substantially all other features are disabledas long as the device remains coupled to the vehicle.

In certain embodiments, coupling of the mobile device to the vehicle cancomplete an ignition circuit such that the vehicle may start. The mobiledevice can act as a switch to close the circuit. For example, asimplified schematic of a part of a vehicle's electrical system is shownin FIGS. 5A and 5B. The electrical system includes a processor 510,which is typically housed in, or electrically coupled to, an enginecontrol unit (ECU) which itself may include or be electrically coupledto an ignition circuit 520. The ignition circuit 520 is open when themobile device is not coupled such that the engine will not start (FIG.5A). When a mobile device 530 is coupled (FIG. 5B), the ignition circuitis closed such that the processor 510 will permit the engine to bestarted once a suitable input is received, e.g., turning of the ignitionswitch, pushing an ignition button, etc. The method can be implemented,for example and as discussed further below, by modifying the lookuptables (LUTs) in the ECU such that the coupling of the mobile device isdesirably present to start the vehicle.

In some examples, a similar system can be implemented as part of thebraking circuit. In many newer vehicles, a user must depress the brakepedal prior to being able to shift the vehicle into gear. Coupling ofthe mobile device to the braking circuit can close the braking circuitand permit shifting of the vehicle into gear. Referring to FIGS. 6A and6B, a braking circuit 620 may be considered open when the mobile deviceis not coupled even when the brake is depressed by a user. Once a mobiledevice 630 is coupled to the system, the processor 610 will permitshifting of the transmission from park to a gear selected by anoperator.

In some examples, it may be desirable to include an in-line switch orbox that can be electrically coupled to the vehicle to permit operationof the vehicle when the mobile device is coupled and prevent operationof the vehicle when the mobile device is not coupled. For example, inolder vehicles not including electronic management systems, it may bedesirable to include a module on the cold side of the ignition switch asshown in the schematics of FIGS. 7A and 7B. The system 700 would includea module 720 inline with an ignition switch. Where a mobile device isnot coupled to the module 720 (see FIG. 7A), the ignition switch wouldbe in an inactive state 710, and the vehicle would not be able to start.When a mobile device 740 is coupled to the module 720 (see FIG. 7B),then the ignition switch would be in an active state 730 such thatturning of the key by an operator would permit starting of the vehicle.The module 720 need not be in the ignition circuit. For example, themodule may be inline with a braking circuit, with a fuel shut offcircuit, etc., such that the vehicle can not be operated withoutcoupling of a mobile device to the module. In operation, the module 720would typically authenticate a SIM card (or other unique identifier) ofthe mobile device to permit operation of the vehicle. In someembodiments, the module 720 can be configured with electrical taps suchthat it can be added to a vehicle by inserting the module 720 inlinewith existing ignition wiring in the vehicle.

In certain examples, the mobile device can be coupled to the systemthrough a wired coupler that is electrically coupled to at least someportion of the vehicle. While the term “wired” is used in certaininstances, there may be no actual wire present. “Wired” refers tophysical contact of some portion of the phone with some portion of thesystem. For example, a mini-USB port on the phone may interface with amini USB port on the system by plugging the phone directly into the USBport of the system without any intervening wire between the two ports.In other examples, a coupling from a navigation unit may exist such thatthe mobile device is coupled to the navigation unit. By coupling themobile device to the navigation unit, the vehicle may then be started orswitched into gear.

In certain embodiments, the exact design of the wired coupler is notcritical and desirably the coupler is selected such that it will workwith about 80% of existing mobile devices such as cellular phones. Insome examples, the vehicle can include two or more different types ofwired couplers to increase the overall compatibility of the system. Insome examples, each of the couplers can be controlled by anadministrator and may be selectively activated and deactivated based onsettings selected by the administrator. In addition, adapters, donglesand the like can be used to permit coupling of a mobile device to awired coupler. Illustrative types of couplers include, but are notlimited to, those having one or more of a USB interface, a mini USBinterface, a micro USB interface, a serial ATA interface, a PS/2interface, a MIDI interface, a serial bus interface, an IEEE 1394interface and the like. While not required, it is desirable that theinterface provide coupling of the mobile device to the system while atthe same time charging (or keeping charged) the mobile device.

In some examples, the coupler can be constructed and arranged to lockthe phone into place during operation of the vehicle. For example, thecoupler can include actuatable tabs, bosses, projections, etc. that mateto slots or receptacles on the mobile device to lock the mobile deviceinto place when the vehicle is running or otherwise being operated. Sucha locking device prohibits removal and use of non hands free functionsof the mobile device while operating the vehicle.

In certain embodiments, the coupler of the device can be configured as acradle, socket, docking station or any device configured to receive themobile device or a slot that can receive some portion of the mobiledevice. For example, the coupler can be configured as a cradle thatreceives the face of the mobile device such that a user cannot manuallyenter commands while the mobile device is coupled. As discussed herein,the coupler may include a cord or wire, but such coupling devices can beless than desired as they may permit the operator to still use themobile device while it is coupled to the vehicle. In such instances, itmay be desirable to disable the display of the mobile device orotherwise render some portion of the mobile device “dumb,” e.g., lockthe keyboard, such that the operator cannot manually interact with themobile device while operating the vehicle.

In certain examples, the exact positioning of the coupler in the vehiclecan vary from vehicle to vehicle and from system to system. In someexamples, the coupler can be positioned in a storage compartment, e.g.,glove compartment, trunk, under seat storage device, storage in a dooror between the front fender well and the front portion of the door orother areas of the vehicle. In certain instances, the storagecompartment can receive substantially all of the mobile device, whereasin other examples a portion of the mobile device may protrude orotherwise be viewed when it is coupled to the vehicle. In some examples,the coupler is positioned such that it renders the mobile deviceinaccessible to a vehicle operator. For example, the coupler may bepositioned in the glove compartment, in a driver seat box, under thedriver's seat, under the driver seat cushion, in an umbrella drawer orcompartment, in the trunk, under the hood in the engine compartment, inthe headliner, at the side of one of the seats or other areas where itwould be difficult or impossible for the driver to use non hands freefunctions of the mobile device when coupled to the vehicle. In otherexamples, the coupler can be positioned in, or otherwise be part of, oneof the cup holders of the vehicle.

In certain embodiments, the coupler can be configured to permit themobile device to perform other functions including data transfer,charging of the mobile device, communicating with the navigation systemof the vehicle and the like. If desired, the mobile device can be usedfor data logging to track speed, gas mileage or other performanceparameters of interest to a vehicle operator.

In certain examples, coupling of the mobile device to the vehicle maypermit uploading or transfer of user specific parameters from the mobiledevice to the vehicle. For example, an identifier on the mobile device,e.g., a SIM card, code or the like, can be used by the vehicle toascertain the particular vehicle operator. User specific oruser-specified parameters include, but are not limited to, the positionof the seat, radio stations, HVAC settings, pre-stored navigationroutes, speed limiter and the like, and such parameters may beautomatically adjusted based on pre-selected or pre-stored user specificparameters that are correlated to the identifier of each mobile device.The lookup tables in the system may include default or selected maps orparameters that can be used if the identifier of the mobile device doesnot match those in the lookup table.

In certain embodiments, in implementing the methods and systemsdescribed herein, the vehicle can be retrofitted with a new processorand/or memory unit, e.g., an ECU, and the ECU can be flashed with a newsoftware program that can implement the methods described herein, themethod can be implemented on a dongle or device that couples to thevehicle through the OBDII port, the method can be implemented as part ofa navigation system, e.g., factory or aftermarket navigation systems, orthe mobile device itself may include a method that prevents operation ofthe mobile device once it is coupled to the vehicle. In embodimentswhere a new ECU is installed, a dealer, factory or OEM company mayproduce a replacement ECU that is vehicle specific and includes suitablesoftware to implement vehicle controls, e.g., valve timing, transmissionshift points, etc. The new ECU may also include a method that can detectthe presence or absence of a coupled mobile device, e.g., throughvoltage sensing, receipt of a signal or message from the mobile device,completion of an open circuit when the mobile device is coupled, etc.The new ECU can be installed at a dealer or can be replaced by a vehicleowner where the ECU is properly configured.

In other embodiments, the ECU may be “flashed” or “re-flashed” where adifferent software program is uploaded to the ECU through an OBDII port,an accessory power port or by otherwise coupling a loading device to theECU. In some instances, for example, the mobile device itself mayinclude the software program that can be used to flash the ECU. Uponfirst coupling of the mobile device with the ECU, the mobile device mayprompt the user to select certain parameters, e.g., vehicle year, makeand model, such that a proper software program is uploaded to the ECU topermit suitable vehicle functioning and to implement the technologydescribed herein. In some examples, a software program may beimplemented using a reader device, e.g., code scanner, or other device,e.g., a laptop, iPad® device or mobile computer, that can be implementedto upload a program or flash an ECU, such as those commonly availablefrom many manufacturers including, but not limited to, Hypertech, Inc.,Bully Dog Technologies, Edge Products and other manufacturers thatcommonly produce performance chips and performance software tools.

In certain embodiments, the method may permit different levels of useraccess. For example, the method may have an administrator setting thatpermits an administrator to add authorized users to the vehicle. Suchusers can be added with user-specified parameters such that theadministrator can set the vehicle based on each user. For example, theadministrator may select speed limiter settings for a particular user,may adjust mirror or seat positions, may switch on GPS tracking featuresfor a particular user to monitor the position of that user, may switchon an alert system if the vehicle is driven beyond a certain distance oroutside a certain area or may otherwise control each operator's abilityto use the vehicle based on an identifier or other criteria associatedwith their mobile device. The system can also include user level accessthat permits the users to operate the vehicle but does not permitoverriding of any user-specified parameters stored in a lookup table orelsewhere in the system. In certain embodiments, the administrativefunctions may reside with a centralized service, e.g., GM's Onstar®service, such that unwanted access by an outsider is not easilyobtained. In other examples, the administrator may be able to controlthe system remotely through the internet or through a wireless devicesuch as a mobile device. In such instances, the administrator cancontrol the user-specified parameters in real time (or almost real time)so they can be adjusted as desired or needed. In addition, theadministrator can activate a temporary key or the override systemremotely to permit operation of the vehicle if the user's mobile deviceis lost or inoperative. Administrator selected settings are typicallystored in one or more lookup tables on a memory unit, which may beseparate from the ECU of the vehicle, may be integral to the ECU or maybe stored remotely from the vehicle.

In certain embodiments, the ability to monitor the vehicle using thesystem provides several advantages in commercial settings. Vehiclepositions can be monitored in real time to determine delivery times,arrival times, delays, a vehicle's current position and the like suchthat efficiency in delivery and monitoring may be increased. Inaddition, a vehicle may be disabled after a certain driving period,e.g., 10 hours, to comply with Department of Transportation regulationsand the like. Data logging can be implemented to keep track of vehicleparameters, routes, traffic information, e.g., based on average vehiclespeed, and other desired information.

In certain embodiments, the systems described herein can be used inconjunction with an additional coupler. For example, in commercialsettings, a vehicle operator may have both a personal mobile device anda company provided mobile device. In such instances, it may be desirableto require the vehicle operator to couple both devices so that theycannot send text messages from their personal device while coupling thecompany-provided device to permit operation of the vehicle. The systemmay be configured to include two couplers with one of the couplers beingconfigured to couple to each of the mobile devices. When both mobiledevices are coupled, the vehicle may be operated as described herein. Anadministrator can selectively activate or deactivate each of the couplerusing the administrative functions of the technology.

In certain examples, the system can include audible reminders or visualdisplays to retrieve the mobile device once the vehicle is switched off.For example, the system may provide an audible beep similar to the onescommonly used to remind a driver their keys are in the ignition. Incertain examples, a driver information display may provide a message toretrieve the mobile device, or the mobile device may be automaticallyejected when the vehicle engine is switched off. Other user friendlyfeatures may also be included in the system to facilitate operation ofthe vehicle and subsequent retrieval of a user's mobile device.

In certain embodiments, the systems described herein may include othersensors, devices, units and the like that work in conjunction withcoupling of the mobile device. For example, a GPS unit of the mobiledevice may work in conjunction with the vehicle to provide feedback to amonitoring site regarding the position of the vehicle. Rather thanimplement a separate tracking system in each vehicle, a company providedmobile device can be used to track the vehicle through the internet orother interface. This feature greatly reduces tracking costs while atthe same time increasing driver safety by preventing text messaging bythe vehicle operator.

In certain embodiments, the mobile device can be wirelessly coupled tothe vehicle. Such wireless coupling may take numerous forms includingwireless coupling with an existing transmitter/receiver of the vehiclesuch as a Bluetooth® device. In such instances, it may be desirable todisable the mobile device when wirelessly coupled to prevent non handsfree operation of the mobile device. For example, when wirelesslycoupled, a handshake between the mobile device and vehicle can beestablished such that the vehicle may be operated. As long as thehandshake is present, the mobile device may remain deactivated toprevent non hands free operation such as sending of text messages.Wireless coupling provides the advantage of not using a coupler specificfor a certain type of mobile device.

In some examples, the mobile device can be used in conjunction with thesystem to be operative as a car key. For example, the system can beconfigured with a circuit electrically coupled to a processor andconfigured to receive an input from a mobile device to prevent operationof a vehicle when the mobile device is not coupled to the circuit and topermit operation of the vehicle when the mobile device is coupled to thecircuit. The processor (or circuit) can be further configured to comparean identifier of the mobile device to an entry in a lookup table topermit operation of the vehicle if the identifier matches the entry inthe lookup table. where the mobile device is wirelessly coupled to thevehicle, the mobile device may permit entry of a code on the mobiledevice, depression of a “Start” button on the mobile device or otherinput can be entered into the mobile device to permit starting of thevehicle. In instances where the mobile device will be disabled, theremay be a delay period, e.g., a few seconds or more, prior to disablingto permit entry of such code or input. In other instances,authentication of the SIM card of the mobile device can permit startingof the vehicle by pressing a button or other device integral to thevehicle without the need for any input on the mobile device.

In certain embodiments, an administrator may add the entries in a lookuptable based on the identifiers of mobile devices of authorized users. Inother examples, an authorized user may couple their mobile device to thesystem, and an entry can be written to the lookup table to permit theuser to operate the vehicle. The written entry may be approved by anadministrator or in certain instances no approval may be required. Asdiscussed herein, the system can be configured to adjust user-specifiedparameters, e.g., seat position, radio stations, speed limiter, etc.,using the entries in the lookup table. Once an entry is verified, theuser may start or operate the vehicle by pressing a button, e.g., eitheron the mobile device or on the vehicle itself without needing a physicalkey to be placed in an ignition switch. As described herein, the car keysystem may include a coupler that is configured to couple the mobiledevice to provide the input from the mobile device to the processor ofthe car key system. This coupler may take many different forms includinga cradle, docking station, socket, USB port and the like and/or may bepositioned in the vehicle out of reach of a vehicle operator or in amanner to be inaccessible to a vehicle operator. In other embodiments,the coupler may be configured such that the mobile device is accessibleto a vehicle operator but is not usable, e.g., the screen is locked, thekeyboard is locked, non hands-free functions are disabled, etc.

In certain examples where a car key system is present, the system caninclude an override system configured to permit operation of the vehiclewhen the mobile device is not coupled to the circuit. This overridesystem may be particularly advantageous for non-authorized drivers tooperate the vehicle or for temporary access to the vehicle. In someexamples, the override system can be configured to permit operation ofthe vehicle at speeds less than a top speed selected by anadministrator, e.g., less than 10 miles per hour, to only permitshifting of the transmission into neutral or to permit otheradministrator specified functions. The override system can, for example,be activated with a keypad or can be activated using a remote signal.

In embodiments where the car key system is used in a commercial vehicle,it may be desirable to base the system on two or more mobile devices.The key to starting the vehicle would be coupling of both mobile devicesoptionally in combination with entry of a code on a keypad, depressing abutton, etc. The circuit can be configured, for example, to permitoperation of the vehicle only when both mobile devices are coupled tothe system. Where two or more devices are needed to couple to thesystem, each of the devices may be coupled by wire, one device may becoupled by wire and the other device may be wirelessly coupled or bothdevices may be wirelessly coupled.

In certain examples, the car key system may desirably include or workwith other sensors and features including weight sensors, ABS sensors,GPS devices, tracking devices, navigation systems, entertainment systemsand other vehicle systems. It is not intended that the use of any of theillustrative embodiments of car key systems described herein limit theother potential systems that can be used in a vehicle.

In certain embodiments, a vehicle comprising an engine, a processorconfigured to control the engine, and a circuit electrically coupled tothe processor and configured to receive an input from a mobile devicemay be used. In some examples, the circuit can be constructed andarranged to prevent operation of the vehicle when the mobile device isnot coupled to the circuit and to allow operation of the vehicle whenthe mobile device is coupled to circuit. In certain instances, thevehicle may include a fixed program such that a user cannot alter orotherwise delete the program to bypass the program.

In certain embodiments of the vehicle, the circuit can be configured toprevent starting of the engine when the mobile device is not coupled tothe circuit and to allow starting of the engine when the mobile deviceis coupled to circuit. In other embodiments, the circuit is configuredto prevent shifting of the vehicle into drive when the mobile device isnot coupled to the circuit and to allow shifting of the vehicle intodrive when the mobile device is coupled to circuit. In some embodiments,the vehicle can include a coupler electrically coupled to the processorand configured to couple to the mobile device to provide the input fromthe mobile device to the processor. As discussed herein, the coupler maytake many different forms including, but not limited to, a cradlesocket, docking station or other device configured to receive the mobiledevice. If desired, the coupler can be positioned in the vehicle out ofreach of a vehicle operator or otherwise be inaccessible to the operatorduring operation of the vehicle. The coupler may permit wired orwireless coupling of the mobile device to the vehicle, may charge themobile device, and can provide other desired functionality. In certainexamples, text messaging functions or all non hands free functions ofthe mobile device can be disabled when the mobile device is coupled tothe circuit.

In some embodiments, the vehicle can include an override systemconfigured to permit operation of the vehicle, e.g., for a configurableperiod or a pre-selected period, when the mobile device is not coupledto the circuit. For example, the override system is configured to permitoperation of the vehicle at less than a selected top speed, e.g., speedsless than 10 miles per hour, can be configured to only permit shiftingof the transmission into neutral and, if desired, can be activated usinga remote signal.

In other embodiments, the vehicle can be configured to implement atleast one user-specific parameter based on an identifier on the mobiledevice. In some examples, the vehicle can include a memory unitelectrically coupled to the processor and configured to receive a methodthat prevents operation of the vehicle when the mobile device is notelectrically coupled to the circuit and to allow operation of thevehicle when the mobile device is electrically coupled to circuit.

In certain embodiments, the vehicle can include a second couplerelectrically coupled to the processor and configured to couple to asecond mobile device. In some embodiments, the system can be configuredto permit operation of the vehicle only when the mobile device and thesecond mobile device are both coupled to the system.

In certain embodiments, the vehicle may include additional sensors anddevices. For example, the vehicle can include a sensor coupled to theprocessor, the sensor configured to provide feedback to a vehicleoperator to retrieve the mobile device when the engine of the vehicle isswitched off. In other examples, the vehicle can include a GPS deviceelectrically coupled to the processor to permit tracking of the vehicle.

In some examples, the type and nature of the engine in the vehicle isnot limiting, and the vehicle may be a vehicle including an electricengine, a combustion engine, a fuel cell, a magnetic engine, an electricmotor, a steam engine, a gas engine, e.g., a hydrogen engine orcombinations thereof. Similarly, the type of vehicle is not limited.Referring to FIGS. 8A-8E, the vehicle may be a passenger vehicle 810, abus 820, a commercial truck 830, a train 840, a subway 850, an airvehicle such as an airplane or other vehicles where operator distractionmay decrease safe operation. The vehicles typically include drive meanssuch as an engine to cause the vehicle to move forward, backward or in adesired direction. For example, an engine can be used to drive two ormore wheels of a vehicle.

In certain examples, a navigation system can be configured to work withor implement the methods described herein. Referring to FIG. 9, anavigation system 900 includes a navigation control unit 920, whichtypically houses a processor and a memory unit. The navigation controlunit 920 is electrically coupled to a global positioning sensor 910 anda display 930. In an illustrative navigation system, a memory unit iselectrically coupled to the processor and comprises navigationinformation. The navigation system 900 can also include a circuitelectrically coupled to the processor and configured to receive an inputfrom a mobile device, the circuit constructed and arranged to preventoperation of the vehicle when the mobile device is not coupled to thecircuit and to allow operation of the vehicle when the mobile device iscoupled to circuit. In some examples, navigation information mayinclude, for example, current position, route display, route planningand other common information provided by existing navigation systems toguide a user to a selected destination.

In certain embodiments, the circuit can be electrically coupled to acoupler configured to couple to the mobile device. In some embodiments,the coupler can be positioned out of reach of a vehicle operator or beinaccessible during operation of the vehicle. In other embodiments, thecoupler can be electrically coupled to a wireless unit to permitwireless coupling of the mobile device to the coupler. In additionalembodiments, the navigation system can include a wireless phone unit topermit hands free calling from the mobile device when the mobile deviceis coupled to the navigation system. In some embodiments, the processor(or circuit) can be configured to compare an identifier of the mobiledevice to an entry in a lookup table to permit operation of the vehicleif the identifier matches the entry in the lookup table. In certainembodiments, the navigation system can be configured to display areminder to retrieve the mobile device when the vehicle is switched off.In other embodiments, the navigation system can include a second couplerelectrically coupled to the processor and configured to couple to asecond mobile device. Where two or more couplers are present eachcoupler may independently be configurable by an administrator. In someexamples, the circuit can be configured to permit operation of thevehicle only when the mobile device and the second mobile device areboth coupled to the system. In other examples, the circuit can beconfigured to permit operation of the vehicle once the mobile device iscoupled without the use of a separate key. In additional examples, thenavigation system can include an override system configured to permitoperation of the vehicle, e.g., for a configurable period or for apre-selected period, when the mobile device is not coupled to thecircuit. For example, the override system can be configured to permitoperation of the vehicle at less than a selected speed, e.g., speedsless than 10 miles per hour, can be configured to only permit shiftingof the transmission into neutral, or can be activated using a remotesignal.

In certain examples, the navigation system can include atransmitter/receiver electrically coupled to the circuit and configuredto receive input from a remote user. For example, thetransmitter/receiver can be configured to send a position of the vehicleto a remote site or can send vehicle information, e.g., location, speed,etc. to a remote site. In some examples, the navigation system can beconfigured to adjust vehicle settings using entries in a lookup table ofthe mobile device. For example, a speed limiter setting or other desireduser-specified parameters may be selected or implemented by thenavigation system. For ease of use, the navigation system can beconfigured to receive verbal commands from an operator of the vehicle.If desired, the navigation system can log vehicle information.

In certain embodiments, the navigation system can include processingmeans, position detecting means electrically coupled to the processingmeans for determining a position of a vehicle, display meanselectrically coupled to the processing means for displaying routeinformation, and a circuit electrically coupled to the processing meansand configured to receive an input from a mobile device, the circuitconstructed and arranged to prevent operation of the vehicle when themobile device is not coupled to the circuit and to allow operation ofthe vehicle when the mobile device is coupled to circuit.

In some examples, the circuit can be electrically coupled to couplingmeans for coupling to the mobile device. In other examples, the couplingmeans is positioned out of reach of a vehicle operator or inaccessibleto the vehicle operator. In additional examples, the coupling means canbe electrically coupled to a wireless unit to permit wireless couplingof the mobile device to the coupler. In further examples, the system caninclude wireless phone means for permitting hands free calling from themobile device when the mobile device is coupled to the navigationsystem. In other examples, the circuit can be configured to compare anidentifier of the mobile device to an entry in a lookup table to permitoperation of the vehicle if the identifier matches the entry in thelookup table. In some examples, system can be configured to display areminder on the display means to retrieve the mobile device when thevehicle is switched off. In other examples, the system can include asecond coupler electrically coupled to the processor and configured tocouple to a second mobile device. In additional examples, the circuitcan be configured to permit operation of the vehicle only when themobile device and the second mobile device are both coupled to thesystem. In further examples, the circuit can be configured to permitoperation of the vehicle once the mobile device is coupled without theuse of a separate key.

In other examples, the system can include override means configured topermit operation of the vehicle when the mobile device is not coupled tothe circuit. For example, the override means can be configured to permitoperation of the vehicle at speeds less than 10 miles per hour, can beconfigured to only permit shifting of the transmission into neutraland/or, if desired, can be configured to be activated using a remotesignal. In some examples, the system can also includetransmitter/receiver means electrically coupled to the circuit andconfigured to receive input from a remote user. In some examples, thetransmitter/receiver means can be configured to send a position of thevehicle to a remote site or can send vehicle information to a remotesite. In certain examples, the system can be configured to adjustvehicle settings using entries in a lookup table of the mobile device.In some examples, the system can be further configured to receive oralcommands from an operator of the vehicle. In additional examples, thesystem can be further configured to log vehicle information.

In certain embodiments, a mobile device is provided that can be used toimplement the methods described herein. For example, a mobile deviceconfigured to be coupled to a vehicle to permit starting of the vehiclewhen the mobile device is electrically coupled at least one electricalsystem of the vehicle can be used. Referring to FIG. 10, a mobile device1000 is shown which includes a keyboard 1010, an interface screen 1020and an internal processor. The mobile device 1000 shown in FIG. 10 ismerely illustrative and other mobile devices including those havingvirtual keyboards can be substituted or otherwise used with thetechnology described herein. In some examples, the mobile device can beconfigured to disable text messaging or non-hands free functions whenthe device is coupled to the vehicle. In other examples, the mobiledevice can be configured to be charged when coupled to the vehicle. Inadditional examples, the mobile device comprises an identifier to permitstarting of the vehicle. In some examples, the mobile device can beconfigured to disable its interface screen 1020 or its keyboard 1010when coupled to the vehicle. In other examples, the mobile device can beconfigured to couple to a wireless unit to permit hands free callingwhen the mobile device is coupled to the vehicle. In some examples, themobile device can be configured to couple wirelessly to the vehicle. Inadditional examples, the mobile device can be configured to couple tothe vehicle in addition to a prior coupled mobile device. In certainembodiments, the mobile device can include user-specified parameters toadjust the vehicle settings. In further embodiments, the mobile devicecan be a cellular phone, a smart phone, a personal digital assistant oran enterprise digital assistant. In some examples, the mobile device canbe rendered dumb when coupled to the vehicle. In some embodiments, themobile device can be configured with a “Start” button, which may be aphysical button on the keyboard 1010 of the mobile device 1000 or mayappear on the interface screen 1020. Such start button may permitstarting of the vehicle by activation of the button, typically after themobile device has been wirelessly coupled to the vehicle.

In certain embodiments, a mobile device capable of text messaging can beused to control operation of a vehicle. For example, the mobile devicecan be configured to be coupled to a vehicle to permit switching of thevehicle into drive when the mobile device is electrically coupled atleast one electrical system of the vehicle. In some examples, the mobiledevice can be further configured to disable text messaging when thedevice is coupled to the vehicle. In certain examples, the mobile deviceis configured to be charged when coupled to the vehicle. In someexamples, the mobile device comprises an identifier to permit switchingof the vehicle into drive. In certain embodiments, the mobile device canbe configured to disable an interface screen when coupled to thevehicle. In other embodiments, the mobile device can be configured tocouple to a wireless unit to permit hands free calling when the mobiledevice is coupled to the vehicle. In additional embodiments, the mobiledevice can be configured to couple wirelessly to the vehicle. In someembodiments, the mobile device can be configured to couple to thevehicle in addition to a prior coupled mobile device. In certainexamples, the mobile device comprises user-specified parameters toadjust the vehicle settings. In additional examples, the mobile devicecan be a cellular phone, a smart phone, a personal digital assistant oran enterprise digital assistant. In further examples, the mobile devicecan be rendered dumb when coupled to the vehicle.

In certain embodiments, a method of preventing a vehicle operator fromsending text messages while operating the vehicle is provided. Incertain examples, the method comprises coupling a mobile device to thevehicle to permit operation of the vehicle, and disabling text messagingof the mobile device to prevent sending of text messages while themobile device is coupled to the vehicle. In some examples, the methodcan include disabling the text messaging by rendering the mobile devicedumb. In other examples, the method can include disabling the textmessaging by deactivating an interface screen of the mobile device. Inadditional examples, the method can include coupling a second mobiledevice to the vehicle to permit operation of the vehicle. In furtherexamples, the method can include coupling the mobile device to thevehicle through a coupler electrically coupled to an electrical systemof the vehicle. In some embodiments, the method can include coupling themobile device to the vehicle to permit starting of the vehicle. Inadditional embodiments, the method can include coupling the mobiledevice to the vehicle to permit shifting of the vehicle into drive.

In some embodiments, the method can include configuring the mobiledevice for hands free calling when the mobile device is coupled to thevehicle. In further embodiments, the method can include configuring themobile device to receive a unique identifier to permit operation of thevehicle. In additional embodiments, the method can include configuringthe mobile device to receive user specific information.

In certain examples, another method of preventing a vehicle operatorfrom sending text messages while operating the vehicle is described. Insome examples, the method comprises coupling a mobile device to thevehicle to permit operation of the vehicle, in which the mobile deviceis coupled to the vehicle at a position inaccessible to an operator ofthe vehicle. In certain embodiments, the method can include disablingthe text messaging by rendering the mobile device dumb. In additionalembodiments, the method can include disabling the text messaging bydeactivating an interface screen of the mobile device. In otherembodiments, the method can include coupling a second mobile device tothe vehicle to permit operation of the vehicle. In some embodiments, themethod can include coupling the mobile device to the vehicle through acoupler electrically coupled to an electrical system of the vehicle. Inadditional embodiments, the method can include coupling the mobiledevice to the vehicle to permit starting of the vehicle. In yet otherembodiments, the method can include coupling the mobile device to thevehicle to permit shifting of the vehicle into drive. In otherembodiments, the method can include configuring the mobile device forhands free calling when the mobile device is coupled to the vehicle. Insome embodiments, the method can include configuring the mobile deviceto receive a unique identifier to permit operation of the vehicle. Inother embodiments, the method can include configuring the mobile deviceto receive user specific information.

In certain embodiments, a method of permitting hands free phone callsfrom a mobile device while operating a vehicle and preventing textmessaging from the mobile device while operating the vehicle isdisclosed. In certain examples, the method comprises coupling the mobiledevice to vehicle to permit operation of the vehicle and disabling thetext messaging of the mobile device when coupled to the vehicle.

In some examples, the method can include disabling the text messaging bydeactivating the text messaging capability of the mobile device. Inother examples, the method can include disabling the text messaging bydeactivating an interface screen of the mobile device. In furtherexamples, the method can include coupling a second mobile device to thevehicle to permit operation of the vehicle. In some examples, the methodcan include coupling the mobile device to the vehicle through a couplerelectrically coupled to an electrical system of the vehicle. In otherexamples, the method can include coupling the mobile device to thevehicle to permit starting of the vehicle. In additional examples, themethod can include coupling the mobile device to the vehicle to permitshifting of the vehicle into drive. In further examples, the method caninclude configuring the mobile device for hands free calling through aBluetooth® unit of the vehicle when the mobile device is coupled to thevehicle. In some examples, the method can include configuring the mobiledevice to receive a unique identifier to permit operation of thevehicle. In additional examples, the method can include configuring themobile device to receive user specific information.

In certain examples, a method of permitting hands free phone calls froma mobile device while operating a vehicle and preventing text messagingfrom the mobile device while operating the vehicle that includescoupling the mobile device to vehicle at a position inaccessible to anoperator of the vehicle to permit operation of the vehicle is provided.

In some embodiments, the method comprises disabling the text messagingby deactivating the text messaging capability of the mobile device. Inother embodiments, the method comprises disabling the text messaging bydeactivating an interface screen of the mobile device. In additionalembodiments, the method comprises coupling a second mobile device to thevehicle to permit operation of the vehicle. In further embodiments, themethod comprises coupling the mobile device to the vehicle through acoupler electrically coupled to an electrical system of the vehicle. Insome embodiments, the method comprises coupling the mobile device to thevehicle to permit starting of the vehicle. In additional embodiments,the method comprises coupling the mobile device to the vehicle to permitshifting of the vehicle into drive. In other embodiments, the methodcomprises configuring the mobile device for hands free calling through aBluetooth® unit of the vehicle when the mobile device is coupled to thevehicle. In yet other embodiments, the method comprises configuring themobile device to receive a unique identifier to permit operation of thevehicle. In further embodiments, the method comprises configuring themobile device to receive user specific information.

In certain examples, a kit for preventing text messaging while drivingis provided. In some embodiments, the kit comprises a memory unit ordevice comprising a method to prevent operation of the vehicle when amobile device is not coupled to the vehicle and to allow operation ofthe vehicle when the mobile device is coupled to vehicle. In otherexamples, the kit may include instructions for flashing the enginecontrol unit of a vehicle with the method on the memory device.

In certain embodiments, the kit can include a coupler configured tocouple the mobile device to the engine control unit of the vehicle. Infurther embodiments, the kit can include a second coupler different fromthe coupler, the second coupler configured to couple a second mobiledevice to the engine control unit of the vehicle. In some examples, eachcoupler can be individually controlled by an administrator. Inadditional embodiments, the kit can include a device configured toreceive the memory unit and to couple to a port of the vehicle to flashthe engine control unit. In some embodiments, the device is configuredto couple to an OBDII port of the vehicle.

In certain embodiments, a kit for preventing text messaging whiledriving that comprises memory means for flashing an engine control meanswith a method to prevent operation of the vehicle when a mobile deviceis not coupled to the vehicle and to allow operation of the vehicle whenthe mobile device is coupled to vehicle, and instructions for using thememory means is described. In certain examples, the kit can includecoupling means configured to couple the mobile device to the enginecontrol means of the vehicle. In other examples, the kit can includesecond coupling means different from the coupling means, the secondcoupling means for coupling a second mobile device to the engine controlmeans of the vehicle. In additional examples, the kit can include devicemeans for receiving the memory means and for coupling with a port of thevehicle to flash the engine control means. In further examples, thedevice means can be configured to couple to an OBDII port of thevehicle.

In certain examples, a method comprising determining if a vehicle isconstructed and arranged to receive an input from a mobile device, thevehicle configured to prevent operation of the vehicle when the mobiledevice is not coupled to the vehicle and to allow operation of thevehicle when the mobile device is coupled to vehicle, and providing aninsurance policy cost estimate based on the determined vehicle isdescribed. In some examples, the method may include configuring thevehicle to prevent operation of the vehicle when the mobile device isnot coupled to the vehicle and to allow operation of the vehicle whenthe mobile device is coupled to vehicle, and adjusting the insurancecost estimate.

In other examples, a method comprising determining if a vehicle isconstructed and arranged to receive an input from a mobile device, thevehicle configured to prevent operation of the vehicle when the mobiledevice is not coupled to the vehicle and to allow operation of thevehicle when the mobile device is coupled to vehicle, and providing aninsurance policy based on the determined vehicle is provided. In someexamples, the method may include configuring the vehicle to preventoperation of the vehicle when the mobile device is not coupled to thevehicle and to allow operation of the vehicle when the mobile device iscoupled to vehicle, and adjusting the cost of the insurance policy.

In some examples, a method of facilitating safe driving comprisingconfiguring a vehicle to be inoperable when a mobile device is notcoupled to the vehicle and is configured to be operable when the mobiledevice is coupled to vehicle is disclosed.

In additional examples, a method of facilitating safe driving, themethod comprising configuring a vehicle to be inoperable when a mobiledevice is not coupled to the vehicle and is configured to be operablewhen the mobile device is coupled to vehicle in a location inaccessibleby a vehicle operator is provided.

In some examples, a method of facilitating safe driving, the methodcomprising providing a vehicle that is configured to be inoperable whena mobile device is not coupled to the vehicle and configured to beoperable when the mobile device is coupled to vehicle in a locationinaccessible by a vehicle operator is provided.

In certain examples, a user may attempt to circumvent the systems andmethods described herein by using extension cords, software programs orother bypass features to permit operation of the vehicle while at thesame time preserving the ability to send text messages. To mitigateagainst such an occurrence, the coupler can be configured as a lockingcompartment (or include a locking door) that remains locked while thevehicle is started or is in gear. As discussed herein, the display orinterface of the mobile device may also be disabled to prevent textmessaging while the mobile device is coupled. Other possibleconfigurations to reduce the likelihood that text messaging and vehicleoperation can be simultaneously performed will be recognized by theperson of ordinary skill in the art, given the benefit of thisdisclosure. For example, the technology described herein can be used incombination with that described in US 20100087137, the entire disclosureof which is incorporated herein by reference.

In certain embodiments, the systems and methods described herein caninclude one or more safety features such that the vehicle engine doesnot switch off if the mobile device is removed while the vehicle is inoperation. For example, once the vehicle reaches a certain speed, e.g.,above 5 mph, the system may permit operation of the vehicle for alimited time after the mobile device is decoupled to avoid crashing orunwanted braking of the vehicle. In some examples, once the vehiclecomes to a complete stop, the system may reimplement one or more methodsrequiring a user to couple the mobile device before the vehicle can beoperated again. Other methods of reimplementing the methods describedherein will be readily selected by the person of ordinary skill in theart, given the benefit of this disclosure.

In certain examples, the systems, method and devices described hereincan be used with one or more biometric features to authorize a user tooperative a vehicle. For example, a user's fingerprint stored in themobile device can be matched with a fingerprint of a finger pressedagainst a screen in the vehicle to verify the operator is an authorizeduser of the vehicle. The fingerprint may also be stored in a lookuptable in the system. Other biometric features and user features, e.g.,user weight, etc., can be used to authorize use of the vehicle.

In certain embodiments, the systems described herein can be configuredas a docking station or other device designed to connect to the mobiledevice. Referring to FIG. 11, a system 1100 comprises a docking station1110 electrically connected to an ignition switch or circuit 1120 and atransmission control unit 1130. The docking station 1110 can beconfigured to prevent starting of the vehicle when the mobile device isdisconnected from the docking station 1110. For example, the dockingstation can be configured to send a signal to the engine control unit(not shown) that permits starting of the vehicle when the mobile deviceis docked and the ignition switch 1120 is actuated by a driver. In otherembodiments, a signal from the ignition switch 1120 can be routedthrough the docking station 1110 and interrupted if a mobile device isnot docked to the docking station 1110 and passed by the docking station1110 if a mobile device is connected to the docking station 1110. Inother configurations, the docking station 1110 can be connected to thetransmission control unit (TCU) 1130 to prevent switching of the vehicleinto drive or reverse until a mobile device is connected to the dockingstation 1110. For example, the TCU 1130 is typically connected to one ormore sensors that can lock the transmission into park until a suitablesignal permits actuating of the transmission from park into drive (orreverse). The docking station 1110 can send a suitable signal to the TCU1130 to permit unlocking of the park feature and switching of thevehicle into drive or reverse. In certain embodiments, the dockingstation 1110 can be physically integrated into the existing vehicle'selectrical system, e.g., hardwired, or may be wirelessly integrated intothe existing vehicle's electrical system. In other instances, thedocking station may be electrically connected to the vehicle systemthrough a port or interface on the vehicle, e.g., an OBDII port, USBport, miniUSB port or other suitable interface.

In certain embodiments, the systems and method described herein can beused with a connector designed to permit interfacing of the mobiledevice with a desired interface of the system. For example, the port ofa particular mobile device may not be compatible for interfacing with aninterface on the vehicle or the systems described herein. A connectorcan be configured to permit connection of a mobile device to the system.In some instances, the connector can be configured with a connector atone end or side to connect to the mobile device and a connector atanother end or side to connect to the system. For example, on one endthe connector may comprise a mini-USB connector to connect to thevehicle or the system of the vehicle and a connector on another end toconnect to the mobile device. In certain embodiments, the connector caninclude one end configured to connect to the vehicle or system and aplurality of other types of connectors to couple to mobile devices. Forexample, the connector can be generally rectangular and comprise aconnector on one side to interface to the vehicle and three differentconnectors, one on each of the other sides of the generally rectangularconnector, to interface to a particular type of mobile device. The usercan select the particular type of connector suitable for theirparticular mobile device. If desired, the mobile device connectors canbe rotated or rotatable such that the mobile device connects to theconnector at an opposite end from the vehicle coupler to provideadditional spacing between the mobile device and the system of thevehicle. Suitable types of connectors for coupling to mobile devicesinclude, but are not limited to, USB type connectors, mini-USB typeconnectors, micro-USB type connectors, and other connectors commonlyused to provide an electrical connection between a mobile device and acharging device and/or a mobile device and a computer.

In certain examples, the connector may be integrated into a mobiledevice jacket, sleeve or case, e.g., a phone jacket or phone case, suchas those commonly used to protect mobile devices. The mobile device casemay be a single piece or may include multiple pieces to permit insertionof the phone and subsequent coupling of the phone sleeve pieces to eachother. Referring to FIG. 12, a phone case 1200 comprises a body 1210configured to receive a mobile device such as a phone, a first connector1215 configured to electrically connect the phone to the phone case1210, and a second electrical connector 1220 configured to electricallyconnect the phone case 1210 to the vehicle or one or more of the systemsdescribed herein. The first connector 1215 and the second connector 1220can be electrically connected to each other through one or moreinterconnects, hardwire connected to each other such that information orsignals from a mobile device can be provided to the first connector 1215and onto the second connector 1220 and to the vehicle or one or more ofthe systems described herein. In an alternate embodiment, the firstconnector 1215 and the second connector 1220 can be wirelessly connectedto each other. Phone cases or sleeves can be configured for particulartypes of phones with a specific type of first connector 1210 designedfor a specific type of phone and a common second connector 1220 suchthat the second connector 1220 that plugs into or interfaces with thedock, system or other devices described herein comprises a commonstructure and/or features. If desired, the phone case or sleeve may alsocomprise an integrated microprocessor such that the methods describedherein can be implemented through the use of the phone sleeve. Forexample, the microprocessor of the phone sleeve can be configured toprevent starting of the vehicle until the phone sleeve is connected thisto the vehicle.

Referring now to FIG. 13, a system 1300 is illustrated in accordancewith some embodiments, where the system is configured to control anoperating state of a vehicle, for example, a motor vehicle. According tosome embodiments, the system provides a method of preventing operationof the vehicle when mobile-device based activities that would otherwisecontribute to distract operation of the vehicle are detected.

The system 1300 includes a mobile device 1302, a controller 1304, adocking station 1306, a user interface 1308, a wireless transceiver1310, an indicating light 1312, an annunciator 1314, memory 1316, afirst electrical input 1320, a second electrical input 1322, a firstrelay 1324 and a second relay 1326. In general, the system 1300 isdeployed in a vehicle to control use of a mobile device in the vehicleby, for example, controlling the operating state of the vehicle based onreceipt of the mobile device 1302 in the docking station 1306. In someembodiments, the docking station 1306 is located in the vehicle withinarm's reach of the operator. For example, in one embodiment, the dockingstation 1306 sized and shaped for installation in a cup holder locatedin a console in the vehicle. According to other embodiments, the dockingstation 1306 may be located elsewhere in the vehicle, for example, onthe visor, in the dash, in the glove box or in the trunk where it isinaccessible to the operator while the vehicle is being operated.

According to the illustrated embodiment, the docking station 1306includes at least one sensor 1307, at least one alignment element 1309,a connector 1311, a communication interface 1313 and receptacle lamp1315. Depending on the embodiment, the at least one sensor 1307 caninclude a limit switch, proximity sensor, optical sensor or othersensing element used to detect when the mobile device 1302 is receivedwithin the docking station 1306. The at least one alignment element 1309can be employed to, for example, “polarize” a receptacle provided by thedocking station to prevent a mobile device 1302 from being insertedincorrectly. According to one embodiment, the docking station 1306includes two pins used as alignment elements 1309 where the two pinshave different diameters. According to this embodiment, the mobiledevice or a case within which the mobile device is housed includescorresponding openings that ensure that the phone can only befully-inserted in the docking station 1306 in a single orientation.According to a further embodiment, the at least one alignment element1309 insurers that a hardwired connection between the mobile device andthe controller is correctly completed by preventing the mobile device1302 from being rotated about its longitudinal axis such that it facesthe wrong direction. When properly aligned a connector included in themobile device 1302, or included in a case within which the mobile deviceis installed for inserting the mobile device in the docking station,properly aligned with the connector 1311 included in the docking station1306.

According to other embodiments, the coupling of the docking station 1306and the mobile device 1302 can be a symmetrical connection such that atleast one alignment element is not required. According to theseembodiments, the mobile device 1302 can be rotated about itslongitudinal axis and faced or positioned in either direction when it isreceived by the docking station 1306.

In some embodiments, where the docking station 1306 provides a hardwiredconnection for the mobile device 1302, the connector 1311 can be used toprovide a connection between the docking station 1306 and the controller1304 via the communication interface 1313. According to one embodiment,the connector 1311 is a mini-USB connector. According to a furtherembodiment the communication interface 1313 includes a cable for examplea ribbon cable.

In various embodiments, the receptacle lamp 1315 illuminates the dockingstation to allow the user to view or otherwise to observe more easily areceptacle provided in the docking station 1306 by which the mobiledevice 1302 is to be received. Such an approach can be used to assistvehicle operators who are in a vehicle after dark.

According to some embodiments, the mobile device 1302 is connected tothe docking station 1306 by plugging the mobile device 1302 into thedocking station to allow an electrical connector included in the mobiledevice 1302 to connect with a compatible electrical connector includedin the docking station 1306. For example, where the mobile device 1302is an Apple™ device, the docking station 1306 can include a 30 pin maledocking station connector or a 10 pin Lightning® connector used with anyof the Apple iPod, iPad and iPhone devices. Other styles and types ofconnectors can be included in the docking station 1306 depending on theembodiment. As will be described in detail herein, according to oneembodiment, the docking station 1306 includes a universal connectorconfigured to couple to any of a variety of mobile devices so long asthe mobile device is fitted with a case or other adapter that convertsthe connector-style employed by the mobile device to a connectorsuitable for attachment to the universal connector included in thedocking station 1306.

In certain embodiments, the docking station, phone jacket or othercomponents of the system can be produced using one or more materialsincluding, but not limited to, metals, metal alloys, non-metals,plastics, elastomers and the like. Where plastics are used, thematerials can be disposed or injected into a mold or die that is sizedand arranged to provide a desired form factor, shape or other features.In some examples, the material used to produce the components can be athermoset or a thermoplastic material. Where a thermoset material isused, the thermoset material can include a fiberglass, a rubber, a foam,a melamine resin, an epoxy resin, a polyimide, a cyanate, a cyanateester, a polycyanurate and combinations thereof or other commonly usedthermoset materials. Where a thermoplastic material is used, thethermoplastic material can include an acrylonitrile butadiene styrene,an acrylic, a cellulose acetate, a cyclic olefin copolymer, anethylene-vinyl acetate, an ethylene vinyl alcohol, a fluoroplastic suchas PTFE, an acrylic/PVC alloy, a polyoxymethylene, a polyacrylate, apolyacrylonitrile, a polyamide, a polyamide-imide, apolyaryletherketone, a polybutadiene, a polybutylene, a polybutyleneterephthalate, a polycaprolactone, a polychlorotrifluoroethylene, apolyethylene terephthalate, a polycyclohexylene dimethyleneterephthalate, a polycarbonate, a polyhydroxyalkanoate, a polyketone, apolyester, a polyethylene, a polyetheretherketone, apolyetherketoneketone, a polyetherimide, a polyethersulfone, ahalogenated polyethylene, a polyimide, a polylactic acid, apolymethylpentene, a polyphenylene oxide, a polyphenylene sulfide, apolyphthalamide, a polypropylene, a polystyrene, a polytrimethyleneterephthalate, a polyurethane, a polyvinyl acetate, a polyvinylchloride, a polyvinylidene chloride, a styrene-acrylonitrile andcombinations thereof or other commonly used thermoplastic materials. Thecomponents may also be painted, etched, dyed or include coatings orother features as desired.

In some embodiments, the controller 1304 is included in the dockingstation 1306. According to other embodiments, the controller 1304 islocated elsewhere in the vehicle. Similarly, in some embodiments, theuser interface 1308 is included in the docking station while in otherembodiments the user interface 1308 is located elsewhere in the vehicle.For example, the user interface 1308 and the controller 1304 can belocated in a common housing remote from the docking station 1306. Inother embodiments, the user interface 1308 and the controller 1304 arelocated in separate locations in the vehicle, respectively. In someembodiments, the user interface may be integrated within existing userinterface in the vehicle, for example, an existing touchscreen display.

According to some embodiments, the user interface 1308 includes a keypadand/or a display. In these embodiments, the user interface 1308 canmount on a face of the docking station 1306. According to oneembodiment, the user interface 1308 includes a keypad that is hingedlymounted to the remainder of the docking station to allow easier accessto a vehicle operator.

The controller 1304 can include electronic components including one orcombination of a microcontroller including a processor (for example, aCPU) and memory 1316. Depending on the embodiment the memory 1316 can beincluded internal to the microcontroller or external to themicrocontroller in a variety of forms including FLASH, EEPROM, RAM andROM. In some embodiments, the memory 1316 is located remote from thedocking station 1306 and no communication path exists that would allow acar thief to log into the system or otherwise access program and/ormemory content via the docking station 1306. According to theseembodiments, the system 1300 has improved security resulting from thepreceding configuration.

In some embodiments, the controller 1304 includes the transceiver 1310for example a Bluetooth™ transceiver. According to these embodiments,the transceiver 1310 allows a fully hands-free operation of anauthorized mobile device 1302 when received by the docking station 1306.

In addition to the preceding features and functionality, the controller1304 can include other elements alone or in combination, for example,signal processing circuitry (for example, an analog-to-digitalconverter), Wi-Fi circuitry, GPS transceivers and other navigationalsystem elements, other instrumentation and/or sensors. In addition, thecontroller 1304 can include an internal communication bus for thetransfer of instructions and data in the controller.

The user interface 1308 can be provided in any of a variety of formsdepending upon the embodiment. For example, the user interface caninclude a conventional keypad similar to the keypad found in a phone. Inother embodiments, the user interface can include a graphical userinterface (GUI) such as a GUI presented in a touchscreen display. Inother embodiments, the graphical user-interface can allow the user tooperate the user interface 1308 via a touchpad or mouse and cursor, orvia speech recognition to execute voice commands.

According to one embodiment, the indicating light 1312 and/or theannunciator 1314 are coupled to the controller 1304. In some embodimentsthe indicating light 1312 and/or the annunciator 1314 are included inthe docking station 1306. These devices can be employed to providefeedback to the user concerning the operating status of the system.Further, although the indicating light 1312 is referred to in thesingular, the indicating light 1312 may include one or a plurality oflight sources. For example, indicating light 1312 can be a single lampcapable of illumination in a plurality of colors. Alternatively, theindicating light 1312 can include a plurality of light sources (forexample, LEDs) that may include one or a plurality of different colors.Thus, where the indicating light 1312 is described as producing red andgreen depending on the operating state of the system, it should beunderstood that separate red and green lamps, respectively, can beemployed in the indicating light 1312. In addition, user feedback can beprovided by establishing various blink-patterns with the indicatinglight 1312 where the different blink-patterns are known to a user toindicate different operating statuses of the controller 1304, forexample.

According the various embodiments, the controller 1304 can also beconnected to one or more elements included in the vehicle, for example,various inputs and outputs (I/O). In the illustrated embodiment, forexample, the first electrical input 1320, the second electrical input1322 are connected to an unswitched source of power and a switchedsource of power, respectively. Other I/O connections can includeconnections between the controller 1304 and vehicle limit switches,transducers and sensors (including fuel sensors, various electrical andelectronic sensors and transducers, combustion sensors, transmissionsensors, brake sensors), dome light circuits, ignition circuits and I/Ocoupled with I/O provided by the vehicle onboard computer.

In an embodiment where the system 1300 is installed in an automobile,the unswitched source of power can include nominal battery voltage, forexample, 12 or 24 VDC. The switched source of power can include the samesource of power isolated from the controller 1304 by operation of akey-switch (for example, an ignition key) or other switching device.According to the illustrated embodiment, the first relay 1324 and thesecond relay 1326 are connected to outputs included in the controller1304. According to one embodiment, each of the first relay 1324 in thesecond relay 1326 are “kill” relays employed to prevent operation of thevehicle where for example the mobile device 1302 is not located in thedocking station 1306. For example, the first relay 1324 can be locatedin an ignition circuit for the vehicle and the second relay 1326 can belocated in a start circuit for the vehicle.

According to some embodiments, the controller 1304 is configured tocommunicate commands and to receive data in reply. However, to improvesecurity of the system 1300, in some embodiments, commands cannot besent to the controller 1304 of the communication interface 1313 betweenthe docking station 1306 and the controller 1304. These embodiments canprovide increased security by preventing the system 1300 from beinghacked using the communication interface between the docking station1306 and the controller 1304. For example, these embodiments prevent ahacker from employing a mobile device 1302 received in the dockingstation to access and/or program the controller 1304 and memory 1316.

According to some embodiments the docking station 1306 is manufacturedfrom plastic, for example, ABS. According to further embodiments, thedocking station 1306 is amended back shirt using an injection moldingprocess.

Referring now FIGS. 14A-14B, operation of the system 1300 is describedin accordance with various embodiments in which an authorized mobiledevice is employed with the vehicle. The process 1400 illustrated inFIG. 14A illustrates the system 1300 as employed to control the startingof a vehicle in accordance with some embodiments. At act 1402, thevehicle operator enters the vehicle and inserts an authorized mobiledevice in the docking station 1306. At act 1404, the controller detectsthat the docking station 1306 is in receipt of the mobile device 1302.In accordance with one embodiment, the controller 1304 detects that themobile device 1302 is received in the docking station 1306 when one ormore limit switches located in the docking station 1306 change state.For example, the limit switches can be located such that they areactivated with the mobile device 1302 fully received in the dockingstation 1306. At act 1406, an optional act is provided by which thecontroller 1304 boots-up based on one or combination of; the opening ofthe vehicle door, activation of a dome light circuit or an ignitionswitch being turned on.

At act 1408, operation of the controller is indicated by turning on theindicating lamp 1312. The indicating lamp can be located integral to thedocking station 1306, in the vehicle control panel, dash, or other userinterface located in the vehicle in the vicinity of the user. Accordingto some embodiments, other forms of user feedback can be provided toindicate when the controller is operational, for example, theannunciator 1314 can be used. According to one embodiment, the speakersincluded in the mobile device 1302 can be used to provide feedbackconcerning the status of the controller 1304. At act 1410, controller1304 operates to receive the mobile-device ID from the mobile device1302. According to some embodiments, at act 1410, the controller 1304polls the mobile device 1302 to receive the mobile-device ID. In otherembodiments, the mobile device 1302 automatically communicates themobile-device ID to the controller 1304 when the mobile device 1302 isdocked and the controller 1304 is operational.

According to one embodiment, the authentication of the mobile-device IDby the controller only occurs before the vehicle is started. In anotherembodiment, removal of a previously authenticated mobile device from thedocking station of an operating vehicle can cause a vehicle shutdownand/or generate an audible alarm (or visual alarm or indicia if desired)in the vehicle. According to these embodiments, a later reinsertion ofthe mobile device into the docking station can require are-authentication of the mobile device in order to allow continuedand/or further operation of the vehicle. The preceding approach can beused to defeat attempts to circumvent the system 1300 by operating thevehicle either with an unapproved mobile device or some form of “dummy”device inserted in the docking station. Either alone or in combinationwith the preceding, the system 1300 can log the occurrence of a removalof the mobile device from the docking station of the operating vehicle.For example, the controller 1304 can store a record (i.e., log) of theevent. As described further herein, this record can later be used toprevent a restarting or other operation of the vehicle. These recordscan also be used in system administration. In one example, such recordscan be used in personnel management.

According to some embodiments, before the vehicle can be started, themobile device 1302 is first authenticated. At act 1412, the controller1304 compares the mobile-device ID received from the mobile device 1302with mobile-device ID(s) of authorized mobile device(s). Theconfiguration of the controller 1304 with the identity of the authorizedmobile devices is described further herein. An unsuccessfulauthentication at act 1412 results in the vehicle remaining inoperative.A successful authentication can result in feedback to the operatorindicating that the vehicle can be started. For example, at act 1414, agreen indicating lamp can be displayed. In other embodiments, otherforms of user feedback can be provided to alert the vehicle operatorthat the mobile device 1302 is successfully authenticated.

According to the illustrated embodiment, a successful authenticationalso results in the controller 1304 generating output signals thattrigger operation of the relays 1324 and 1326. For example, the outputsignals can close the relays to allow the vehicle to be started andoperated, at act 1418. In accordance with some embodiments, thecontroller 1304 wirelessly communicates with the relays 1324, 1326.

Where the authentication of the mobile device is unsuccessful theprocess 1400 moves to act 1416. Here, indicating light 1312 remains in astate (for example, red in color) to provide the operator with noticethat the authentication was unsuccessful. According to furtherembodiments, one or more approaches can be used to provide the operatorwith one or a series of follow-on opportunities to authenticate themobile device.

Referring now to FIG. 14B, a process 1420 illustrates the response ofthe system 1300 when the authenticated mobile device is removed from thedocking station 1306 while the vehicle is operating. At act 1422,removal of the phone from the docking station in an operating vehicleresults in immediate feedback to the vehicle operator. According to oneembodiment, removal of the phone from the docking station is detected byone or more sensors (for example, limit switches) that change state whenthe mobile device is fully seated in the docking station. According toanother embodiment, the system 1300 periodically receives a uniquemobile-device ID from the mobile device 1302 so long as the mobiledevice is received within the docking station 1306. In a furtherembodiment, each of the sensor inputs and the receipt of themobile-device ID must occur to allow the continued operation of thevehicle and failure to receive each results in the immediate feedback tothe vehicle operator at the mobile device is removed from dockingstation. Failure to return the mobile device to the docking station canresult in a shutdown of the vehicle.

In the illustrated embodiment, a change of state of the indicating lamp1312 and activation of the annunciator 1314 occur in response to removalof the mobile device from the docking station. In accordance with oneembodiment, the annunciator 1314 provides an audio signal that isgreater than 70 dB, for example, 72 dB. The preceding insures that thevehicle operator will be made aware of and respond to such anoccurrence.

The system 1300 can be configured to provide predetermined time delaysin advance of a variety of actions that may occur during operation ofthe system. At act 1424, the controller sends a signal to open one ormore relays because the phone has not been re-docked. In embodimentswhere the controller is coupled to a start relay, there may be noimmediate effect on the operation of the vehicle. According to otherembodiments where the controller is coupled to an ignition relay aloneor in addition to the start relay, act 1424 can result in a shutdown ofthe vehicle. According to these embodiments, the relay actuation willoccur unless the authenticated mobile device is returned to the dockingstation within a predetermined period of time. For example, thecontroller 1304 can be programmed to deactivate the relays 1324, 1326 toisolate a start circuit or to shut the vehicle down. Regardless ofwhether the mobile device is returned to the docking station within thepredetermined period of time, the removal of the mobile device from thedocking station with the vehicle operating is logged as an event by thecontroller 1304, at act 1426. According one embodiment, theevent-logging that occurs at act 1426 includes associating a timestampeach occurrence of a de-docking of the mobile device from the dockingstation of an operating vehicle. According to another embodiment, theevent logging does not include a timestamp but simply adjusts a count(increments or decrements) maintained by a counter included in thecontroller 1304. Each of the preceding embodiments allows a systemadministrator to identify whether and how many times a mobile device isremoved from the docking station 1306 of the operating vehicle.

As is described in more detail herein, such event logging can be used toprevent a further operation by preventing the vehicle from beingrestarted following the first time the vehicle is shutdown, e.g., afterthe ignition is turned off, after such an event. Accordance to a furtherembodiment, vehicle restarting is prevented after some otherpredetermined maximum number of events in which the mobile device isremoved from the docking station while the vehicle is operating. In anyof the preceding embodiments, a system administrator can allow the userto override the “lockout” by providing the user with a one-time code toallow them to arrive at their destination or other predeterminedlocation where the occurrence of the event(s) can be addressed. Ifdesired, a system administrator can immediately address whether theoperator should be permitted to operate a vehicle.

At act 1428, the controller 1304 responds to the mobile device beingreceived back in the docking station 1306 by deactivating the alarmsoriginally triggered by its removal from the docking station. Forexample, the indicating light 1312 can return to a green color andactivation of the annunciator 1314 is stopped. According to oneembodiment, the mobile device is re-authenticated when it is returned tothe docking station. In a further embodiment, failure to successfullyre-authenticate the mobile device can result in a shutdown of thevehicle or the logging of a different type of event.

The system 1300 can also be configured such that a series of events inwhich the mobile device is removed from the docking station acts to shutthe vehicle down. Where, for example, a series of three or more suchevents occurs during a single trip, the authenticated mobile device canbe removed from a list of authorized mobile devices. Further at act1430, the vehicle operator with the previously authorized mobile devicecan be forced to contact a system administrator to obtain authorization(for example, a one-time-use code for entry via the user interface 1308)to complete the trip despite the mobile device being removed from theauthorized list.

In some embodiments, a monitoring of the presence of the mobile device1302 in the docking station 1306 includes not only the use of the atleast one sensor 1307, but also a monitoring of the connectivity of thehardwired electrical connection between the mobile device 1302 and theconnector 1311. In one embodiment, a USB connection is used to connectthe mobile device 1302 to the docking station 1306. According to oneembodiment, a mini-USB connection is employed. In this embodiment, thecontroller 1304 monitors the connection of the mobile device to the USBconnector included in the docking station to confirm the presence of themobile device in the docking station.

According to one embodiment, the continued operation of the vehiclefollowing a successful authentication in accordance with FIG. 14A usestwo forms of feedback that confirm the presence of the authenticatedmobile device in the docking station. The first was described withreference to FIG. 14B where the sensors included in the docking station(for example, limit switches, magnetic sensors, etc.) detect thecontinued presence of the mobile device in the docking station.Otherwise the system detects that the mobile device is removed from thedocking station at act 1422. In further embodiments, the system candetect the presence of the mobile device in the docking station based ona periodic receipt of a unique mobile-device ID from the mobile device.

According to some embodiments, the mobile-device ID includes at leastone of a SIM number, IMEI number and a USB serial number to identify themobile device to the controller 1304. Here, SIM number refers to thenumber associated with the Subscriber Identity Module included in themobile device and the IMEI number refers to an International MobileEquipment Identity number associated with a mobile device. In accordancewith some embodiments the mobile-device ID uniquely identifies themobile device to the controller 1304. According to one embodiment, theUSB serial number is employed because it is more easily accessedelectronically than SIM number or IMEI number and/or it is common to themobile devices regardless of manufacturer. In some embodiments, thecontroller actively polls the mobile device for the mobile-device ID,for example, periodically polls the mobile device for the ID. Accordingto these embodiments, the mobile device communicates the mobile-deviceID to the docking station in response to a request from the dockingstation while in other embodiments the mobile device is programmed toperiodically communicate the mobile-device ID to the docking stationwithout being requested to do so. The above-described approach allowsthe system to detect the presence of the mobile device in the dockingstation independent of the sensors and independently warn the vehicleoperator of an impending vehicle shutdown or other action (eventlogging, etc.) that will result due to removal of the mobile device fromthe docking station.

Referring now to FIG. 14C, a process 1440 is illustrated in accordancewith a further embodiment. The illustrated process 1440 shows a resultwhere a trip in the vehicle with an authorized mobile device has reachedan end. At act 1442, a user turns off the ignition and removes theauthenticated mobile device from the docking station 1306. At act 1444,the controller 1304 enters a “sleep” mode when it detects the removal ofthe mobile device from the docking station after the vehicle isshutdown. Where the vehicle is shutdown and the user does not remove themobile device from the docking station, a timer operates a predeterminedamount of time at act 1446. With the timer running, the controller 1304remains “awake”. During this period, at act 1448, the authentication ofthe mobile device 1302 remains active and the local status indication,for example, the status of the indicating light 1312, provides feedbackthat the authentication remains valid and the vehicle is operational.

Upon either removal of the phone from the docking station or expirationof the timer, the controller 1304 operates to open the relays 1324,1326, turn the indicating light 1312 off and enter a reduced-power sleepmode at act 1450.

Should the timer expire while the mobile device 1302 remains docked, thecontroller 1304 remains in the sleep mode until a subsequent act occurs.In one embodiment, any of the following acts place the controller 1304in an active mode: the ignition is turned on; a vehicle door is openedto activate a dome-light circuit; or the mobile device is momentarilyremoved from and then returned to the docking station 1306.

The system 1300 can also, in various embodiments allow for limitedoperation of a vehicle on a temporary basis by operators who do notpossess an authorized mobile device. FIG. 15 illustrates a process 1500in accordance with an embodiment in which temporary operation of thevehicle is permitted on entry of a previously approved one-time code. Atact 1502, the controller 1304 enters an active mode when it is, forexample, awakened by any one of or combination of: insertion of a keyinto an ignition switch; activation of an ignition circuit for thevehicle; or opening of a door to the vehicle. At act 1504, thecontroller 1304 enters the active operating state and turns on theindicating light 1312 to indicate that the system is not ready to allowoperation of the vehicle. For example, the docking station or other userinterface including the system 1300 can display a red LED to indicatethe operator the operator that the vehicle is currently inoperative.

According to the illustrated embodiment, the system 1300 has one or moreone-time use codes previously established by a system administrator. Thecontroller 1304 is programmed with these codes, for example, by theadministrator using the user interface 1308. In one embodiment, theadministrator employs a tablet computer or the mobile device towirelessly program the controller 1304, for example, via the Bluetoothcommunication network. In the illustrated embodiment, the operatorenters a six digit code (for example, a PIN number) into the system 1300via the user interface 1308, at act 1506. At act 1508, the controller1304 authenticates the PIN to determine whether it is valid. Where thePIN is successfully authenticated, the controller changes the state ofthe system 1300 to allow operation of the vehicle even though anauthenticated mobile device is unavailable. In the illustratedembodiment, successful authentication results in a change in the statusof the indicating light 1312 (for example, a change from red to green)and activation of the relays 1324, 1326. At act 1510, the vehicleoperator can start the vehicle, one time only, with the successfulauthentication.

Upon completion of the temporary-use by the operator, the ignition isturned off and the controller 1304 provides outputs to operate therelays 1324, 1326 to shut the vehicle down. The one-time code is nolonger available to permit operation of the vehicle. In addition, at act1512 the controller operates indicating light 1312 to indicate that thevehicle is inoperative. According to some embodiments, the process 1500includes act 1514 at which the one-time code is deleted or otherwiserendered unavailable for future use. In general, one-time codes can beupdated (newly added or deleted) by a system administrator.

Further approaches can be used to allow an operator who is not inpossession of an authorized mobile device to operate the vehicle on atemporary basis. FIG. 16 illustrates a process 1600 according to someembodiments, for example, a valet-parking or vehicle-service situation.At act 1602 the controller 1304 enters an active mode when it is, forexample, awakened by any one of or combination of: insertion of a keyinto an ignition switch; activation of an ignition circuit for thevehicle; or opening of a door to the vehicle. At act 1604, thecontroller 1304 enters the active operating state and turns on theindicating light 1312 to indicate that the system is not ready to allowoperation of the vehicle. For example, the docking station or other userinterface including the system 1300 can display a red LED to indicate tothe operator that the vehicle is currently inoperative.

According to the illustrated embodiment, the system 1300 has one or morePIN codes previously established by a system administrator for thevalet-parking situation. The controller 1304 is programmed with thesecodes by, for example, the administrator. In the illustrated embodiment,the operator enters a six digit code into the system 1300 via the userinterface 1308, at act 1606. At act 1608, the controller 1304authenticates the PIN to determine whether it is valid. Where the PIN issuccessfully authenticated, the controller changes the state of thesystem 1300 to allow operation of the vehicle. In the illustratedembodiment, successful authentication results in a change in the statusof the indicating light 1312 (for example, a change from red to green)and activation of the relays 1324, 1326. At act 1610, a timer beginsoperation to measure a predetermined period of time established by thesystem administrator and associated with the authorized PIN entered bythe operator. In the illustrated example, the predetermined period oftime is 3 minutes.

Where the authentication of the mobile device is unsuccessful theprocess 1600 returns to act 1604 where the controller is operational andthe system awaits entry of a valid PIN. According to one embodiment, thesystem can limit the number of access attempts following activation ofthe controller 1604 from the “sleep” mode.

At act in the 1612 the vehicle operator can start the vehicle, at anytime within a continuous but temporary period beginning with successfulauthentication of the PIN. In various embodiments, the allowableoperating period is established by a system administrator and can varywith each PIN. In general, the approach illustrated by the process 1600facilitates a temporary operation of the vehicle by operators who arenot in possession of an authorized mobile-device.

In an act 1614, the predetermined period of time expires. In response,the controller 1304 signals the relays 1324, 1326 to open and preventany further operation of the vehicle. In addition, the controllerchanges the status of the indicating light 1312 to indicate that thevehicle is not operational. In a further embodiment, the system does notautomatically shut down the vehicle after the predetermined period oftime. Instead, the system activates an annunciator (which can includeindicia such as, for example, an audible sound, flashing lights or awarning light) that operates until the vehicle is shut down. Accordingto this embodiment, the vehicle cannot be restarted thereafter without anew PIN code provided by the administrator.

It will be recognized by the person of ordinary skill in the art, giventhe benefit of this disclosure, that the processes and methods describedwith reference to FIGS. 14A-16 are merely illustrative and certain stepsmay be omitted and other steps may be added. For example, the method maybe implemented without the ability to override the system such thatcoupling of the mobile device to the vehicle is required to operate thevehicle.

The system 1300 can include a variety of administrative capabilities toallow the system administrator to customize the system configuration.Referring to the process 1604 for example, a system administrator canchange pin number and/or timer duration. In addition, an administratorcan establish a delay that requires a minimum predetermined amount oftime between a time the vehicle is turned off during the allowableoperating period and the next time that it is started during that sameperiod.

Other available administrative options can include: adding a mobiledevice to a list of approved mobile devices for the vehicle; removing amobile device from the list of approved mobile devices for the vehicle;setting the predetermined period of time that the system 1300 willoperate in the valet/service mode; establishing the PIN used as thevalet/service code; adding to or deleting from the list of approvedone-time use passwords; establishing a period of time that must elapsebetween successful authentication of the one-time use codes; adjustingthe operating-period during which the controller remains “awake”following a vehicle being shut down; and various resets that allow areturn to one or more factory original settings for the system.

Referring now to FIG. 17, a docking system 1700 for a mobile device isillustrated in accordance with some embodiments. In the illustratedembodiment, the docking system includes a docking station 1702 and amobile-device case 1704. The mobile-device case may for example beemployed with a mobile phone and is described in more detail herein. Inother embodiments, a docking station 1702 is employed with a mobiledevice and a mobile-device case is not used. In general, in someembodiments, the docking system 1700 provides a receptacle located in avehicle where the vehicle-operator's mobile device is placed to allowthe vehicle to be started and operated. According to these embodiments,the docking system 1700 is used to prevent operation of the vehicle whenmobile-device based activities that would otherwise contribute todistracted operation of the vehicle are detected. According to someembodiments, the docking station 1702 includes mounting hardware 1701.According to one embodiment, different style mounting hardware isemployed depending on whether the docking station is mounted in aconsole, on a dash or elsewhere in the vehicle. Further, the dockingstation can include one or more indicating lights 1708. According tosome embodiments, the indicating light(s) 1708 can be used, either aloneor in combination with a speaker, as an annunciator to alert the vehicleoperator to the system status. For example, the indicating light(s) 1708can illuminate and/or blink when the mobile device is removed from thedocking station 1702 of operating vehicle. If desired, or more lights onthe vehicle may blink (for example, a dome light) or be switched on tonotify the user that the mobile device has been removed from the dockingstation 1702.

According to some embodiments, the docking station 1702 rendersinaccessible a hands-on user interface included in the mobile device.For example, the docking station can prevent access to a physicalkeypad, touch pad or touchscreen graphical user interface when themobile device is received in the docking station. According to theseembodiments, however, a wireless communication user interface of themobile device is operational with the mobile device received in thedocking station 1702. For example, a user operating vehicle may be ableto use the mobile device in a hands-free manner with the mobile devicereceived in the docking station 1702, for example, via Bluetooth™communication using a headset or microphone mounte din the cab of thevehicle.

FIG. 18 illustrates an exploded view of the docking system 1700 inaccordance with some embodiments. In the illustrated embodiment thedocking station 1702 includes a sleeve 1703, a base 1705 and a wall1707. The docking station 1702 also includes a first circuit board 1710,at least one alignment element, a second circuit board 1714, a firstconnector 1711, a second connector 1716, a lamp 1715 and a sensor 1717.In one embodiment, the first circuit board 1710 and the second circuitboard 1714 are connected to one another using a ribbon cable.

According to various embodiments, the docking station 1702 provides areceptacle 1709 in which the mobile device is inserted. In theillustrated embodiment, the wall 1707 attaches to the base 1705 to formthe receptacle 1709 within which the mobile device 1302 (enclosed in themobile-device case 1704) is inserted in a linear sliding motion. In theillustrated embodiment, the sleeve 1703 is used to provide some amountof adjustment for the width of the receptacle.

The docking station 1702 also houses a portion of electronics includedin the system 1300. In the illustrated embodiment, electronics arehoused in the base 1705 and the first circuit board 1710 is connected tothe indicating light 1708. An annunciator (for example, the annunciator1314) may also be connected to the first circuit board 1710. The secondcircuit board 1714 is connected to the lamp 1715. Further, theindicating light 1708, annunciator, lamp 1715 and sensor 1717 can bemounted (for example, surface mounted, through-hole mounted, etc.) totheir respective circuit boards 1710, 1714. According to a furtherembodiment, the docking station 1702 only includes a single circuitboard housed in the base 1705.

The sensor 1717 can be provided in a variety of configurations dependingon the embodiment. For example, the sensors 1717 can bemechanically-activated limit switches, optical sensors,magnetically-operated proximity switches or another style sensorprovided that sensor changes state when the mobile device is fullyreceived within the docking station 1702. In the illustrated embodiment,a limit switch is used and the switch is depressed when the mobiledevice enclosed in the case 1704 is fully inserted within the receptacle1709. According to one embodiment. A plurality of sensors 1717 can beemployed to detect the presence of the mobile device 1302 in thereceptacle 1709.

In various embodiments, the first connector 1711 (for example, amini-USB) provides the electrical connection for connection of themobile device 1302 to the docking station 1702. In some embodiments, themobile device 1302 is plugged directly into the docking station 1702 tocomplete a hardwired connection between the mobile device 1302 and thedocking station 1702. However, in the illustrated embodiment, the mobiledevice 1302 is inserted in the mobile-device case 1704 where a hardwiredconnection is completed between a connector included in the mobiledevice 1302 a connector included in the mobile-device case 1704. Furtherin the illustrated embodiment, the first connector 1711 completes ahardwired connection with the connector included in the mobile-devicecase 1704 when the mobile-device case is fully inserted within thedocking station 1702. According to one embodiment, the first connector1711 is limited to a USB connection. Alternate communication buses canbe provided for the hardwired connection between the docking station1702 and the mobile device 1302 in alternate embodiments.

According to some embodiments, the receptacle 1709 is configured for aselected mobile phone including a case (for example, an Apple iPhone, aSamsung Galaxy 3 or other phone) and corresponding case. According tothis embodiment, a mobile phone other than the selected mobile phone maydesirably interface with the system through the use of the sleeve 1703for the sleeve helps properly align the other mobile phone in thereceptacle 1709. Accordingly, the docking system 1700 provide universalreceptacle for a wide range of phones. The type and style of case can bedetermined by the designer depending on the embodiment. In accordancewith one embodiment, the selected phone is a Samsung Galaxy 3 with a milspec cover from Casemate. In further embodiments, the preceding approachcan also be employed with other devices such that the docking system1700 is configured for a plurality of tablet computers or other mobiledevices with or without sleeve 1703 depending on the embodiment.

The connector 1716 can be mounted to the second circuit board 1714 toprovide a hardwired connection between the docking station 1702 and thecontroller 1304. In some embodiments the connector 1716 provides ahardwired connection between the docking station and other systemelements.

The at least one alignment element 1712 can be employed to, for example,“polarize” a receptacle provided by the docking station to prevent amobile device 1302 from being inserted incorrectly. According to oneembodiment, the docking station 1306 includes two pins used as alignmentelements 1712 where the two pins have different diameters. According tothis embodiment, the mobile device or a case within which the mobiledevice is housed includes corresponding openings that ensure that thephone can only be fully-inserted in the docking station 1306 in a singleorientation. According to a further embodiment, the at least onealignment element 1309 insurers that a hardwired connection between themobile device and the controller is correctly completed by preventingthe mobile device 1302 from being rotated about its longitudinal axissuch that it faces the wrong direction.

Referring now to FIG. 19, the mobile-device case 1704 is illustrated inaccordance with one embodiment. In general, the mobile-device case 1704is an adapter that converts the hardwired electrical connection providedby the mobile device to a hardwired electrical connection suitable forconnection with the connector included in the docking station 1702. Inthe illustrated embodiment, the mobile-device case 1704 including anuppercase 1720, a lowercase 1722, a rear panel 1724 and a connector1726. Depending on the embodiment, the mobile-device case 1704 can beconfigured for a variety of mobile devices to provide a universalhardwired electrical connection for connection of the mobile device tothe docking station 1702. In the illustrated embodiment, themobile-device case 1704 is configured for use with a mobile phone.Therefore, the connector 1726 provides a hardwired connection between aconnector included with the mobile phone and the first connector 1711included in the docking station. The rear panel 1724 can be provided toallow access to the connector 1726 during any of manufacturing, assemblyand testing.

In the illustrated embodiment, the mobile phone inserted in thelowercase 1722. The uppercase 1720 and then attached to the lowercaseand the upper half of the phone. According to some embodiments, thedisplay screen of the mobile device 1302 is not viewable when the mobiledevice is received by the docking station 1702.

Referring now to FIG. 20, a system 2000 is illustrated in accordancewith further embodiments. In some embodiments, the system 2000 isemployed to limit, reduce or entirely prevent operation of a vehiclewhen mobile-device based activities that would otherwise contribute todistracted operation of the vehicle are detected. In accordance with oneembodiment, the system 2000 is employed in managing a plurality of fleetvehicles to reduce or prevent distracted driving caused by mobile-phoneuse of the operators of the fleet vehicles.

In the illustrated embodiment, the system 2000 includes anadministrative user 2002, a vehicle operator 2004, a mobile device 2006that is associated with the vehicle operator, at least one vehicle 2007,an on-board vehicle system 2008, a vehicle identifier 2010, a network2012, a local administrative center 2014, a local system 2016 includingdata storage 2018, and a remote system 2020 also including data storage2023. In various embodiments, the elements of the system 2000 cancommunicate with one another over the network 2012 via one or morecommunication interfaces 2021.

According to some embodiments, the on-board vehicle system 2008 includesany or a combination of the controller 1304, memory 1316, dockingstation 1306 and the system elements illustrated as being includedtherein, user interface 1308, wireless system 1310, unswitched input1320, switched input 1322, and relays 1324, 1326, for example, asoriginally described with reference to the system 1300 illustrated inFIG. 13. Accordingly, the on-board vehicle system 2008 can be employedas described with reference to the system 1300 and the embodimentsillustrated in FIGS. 13-19.

Embodiments of the system 2000 can be employed for a single end-userwith one or multiple vehicles and/or multiple operators under theiradministration. The system can also be employed for one or a fleet ofcommercial vehicles, for example, a fleet of delivery or other transportvehicles. Further, the system 2000 can be employed with any type ofvehicle depending on the embodiment. Accordingly, it should be apparentto one of ordinary skill in the art with benefit of this descriptionthat the system 2000 is not limited to use solely with commercial fleetsor solely where multiple vehicles are under common administrativecontrol. For example, the administrative user 2002 may also be a vehicleoperator of the vehicle 2007. Further, the administrative user 2002 maybe the only vehicle operator of the vehicle 2007.

The system 2000 can also include, or be configured to work with, operatewith, or be programmed by, an administrative mobile device 2022, forexample, a tablet computer (for example, an iPad device), mobile phoneor other portable computing device. The administrative mobile device2022 includes configuration capabilities to allow the administrativeuser 2002 to program the onboard system 2008 with configurationinformation to: 1) add and remove operators and their associated mobiledevices from the list of authorized users of the at least one vehicle2007; 2) adjust predetermined time limits associated with any ofone-time codes, temporary operating periods, etc.; 3) adjust overridesettings; 4) establish and set one-time codes; 5) manage memory (forexample, memory 1316); 6) clear an event log and 7) interface with thevehicle ECU. According to some embodiments, the administrative mobiledevice 2022 wirelessly communicates with the on-board vehicle system2008, for example, via Bluetooth™.

In some embodiments, the system includes the local administrative center2014 that can house the local system 2016 and data storage 2018. Wherethe system includes multiple users and/or multiple vehicles (forexample, at a distribution center) the local system 2016 can store theconfiguration information listed in the immediately preceding paragraphfor one or a plurality of vehicles 2007 and one or a plurality ofvehicle operators 2004. This configuration information for multiplevehicles and/or users can be stored in a database provided in the datastorage 2018 from which it can be communicated to administrative userdevice 2022 of the administrative users 2002. According to oneembodiment, a hardwired interface is employed communicate data betweenthe local system 2016 and the administrative user device 2022. Inanother embodiment, a wireless communication interface is employed tocommunicate data between the local system 2016 and the administrativeuser device 2022.

In general, the network 2012 can include local-area networks (LANs),wide area networks (WANs) and may include the Internet. According to afurther embodiment, the network 2012 provides access “over-the-cloud” toone or more remote locations 2020 where further configurationinformation can be stored. According to one embodiment, the local system2016 periodically synchronizes with servers at the remote location 2020.According to this embodiment, the remote location 2020 providesredundant storage and storage element 2023 for the local system 2016 inthe event that the local system is corrupted. In addition, the network2012 and communication interfaces 2021 allow the system 2002 “push”software updates and/or updated lists of authorized users, and updatedsystem configurations that can be used by an administrative user 2002 toconfigure the on-board vehicle system(s) 2008 in the vehicle(s) 2007.According to one embodiment, a local system 2016 is not employed howeverthe remote system 2020 is employed. In another embodiment, the remotesystem 2020 is not employed. In yet another embodiment, neither thelocal system 2016 nor the remote system 2020 are employed andconfiguration information is managed and stored solely on theadministrative mobile device 2022.

In further embodiments, the administrative mobile device 2022 wirelesslycommunicates with either or both of the local system 2016 and/or theremote system 2020 and network 2021. In general, the administrativemobile device 2022 is employed using a wireless or a hardwiredcommunication interface 2021 to configure the on-board vehicle system2008 for one or more authorized mobile devices and associated operators2004. For example, the controller 1304 included in the on-board vehiclesystem 2008 can store one or a plurality of lookup tables concerning theconfiguration information stored in the memory 1316. The lookup tablescan include a vehicle-operator identification, associated mobile-deviceID or IDs and other configuration information concerning the authorizeduser (for example, the vehicle operator 2004). Further, the lookuptables can include similar configuration information for a plurality ofauthorized users.

In some embodiments, the vehicle identifier 2010 is employed to allow anelectronic identification of the vehicle 2007 by the administrative user2002. According to one embodiment, the vehicle identifier 2010 is abarcode or other similar identification device that can be opticallyscanned. Further, where the administrative user 2002 employs a tabletcomputer or other mobile device with a barcode reader, the configurationinformation and settings for a specific vehicle 2007 can be more easilyestablished and catalogued in the field. According to one embodiment,the administrative mobile device 2022 is employed to first identify thevehicle 2007 and then “push” updated configuration settings for thevehicle to the on-board vehicle systems 2008. According to oneembodiment, these configuration settings are stored in theadministrative mobile device 2022.

In one example, the administrative user 2002 administers a fleet ofvehicles and the vehicle operator 2004 is scheduled to leave thetransportation depot with the vehicle 2007. In this example, theadministrative user 2002 can receive the configuration information forthe vehicle operator 2004 and the vehicle operator's associated mobiledevice 2006 from the local system 2016 or via direct entry into theadministrative mobile device 2022, for example, using a touchscreen orother user interface. Using a scanning feature available in theadministrative user device 2022 (a barcode and/or IR scanner), theadministrative user 2002 scans in the vehicle identification andassociates the vehicle operator 2004 and mobile device 2006 with thevehicle 2007. According to another embodiment, the administrative userdevice identifies the vehicle using near field communication. Theadministrator user 2002 then employs the administrative user device 2022to load/program the on-board vehicle system 2008 with the updatedconfiguration including the operator 2004 and mobile device 2006.

Referring now FIG. 21, operation of a process 2100 for use with a systemto control use of a mobile device in a vehicle is described inaccordance with various embodiments, for example, the system 1300 andthe system 2000. The process 2100 starts at act 2102, for example, whena key is inserted in a vehicle ignition and/or moved to a vehicle startposition. In embodiments where vehicle starting employs an element otherthan a key (for example, the pressing of a button in an electricvehicle) act 2102 begins when the activation of the button or otherstart mechanism is detected by the system controller (for example, thecontroller 1304).

At act 2104, the process determines whether the docking station (forexample, the docking station 1306) is in receipt of the mobile device(for example, mobile device 1302, 2006). In accordance with variousembodiments, the presence of the mobile device in the docking station isdetected using one or more sensors in the docking station (any of limitswitches, magnetic switches, optical sensors, etc.), the receipt of anelectrical signal from the mobile device, or the detection of currentbeing drawn by the mobile device (for example, charging current). Thepreceding approaches can be used alone, in combination with one anotheror in combination with other forms of detection depending on theembodiment.

Where the presence of the mobile device in the docking station is notdetected, the vehicle cannot be started and the process returns to thestart 2102. Where the presence of the mobile device in the dockingstation is detected, the process 2100 moves to act 2106 where thevehicle operator is permitted to start the vehicle.

At act 2108, the continued presence of the mobile device in the dockingstation is monitored while the vehicle is operational. Depending on theembodiment, where the presence of the mobile device is detected, theprocess 2100 continues to repeat act 2108 either periodically or on acontinuous basis while the vehicle is operating.

When the presence of the mobile device is no longer detected in thedocking station the process moves to acts 2112 and 2114 either directlyor following an optional time delay at act 2110. At act 2112, theremoval of the mobile device from the docking station is recorded as anevent (for example, in either or both of the memory of the controllerand remote storage such as the storage 2018 or other database accessedvia the “cloud”). In some embodiments, the event can also be recorded inmemory included in the mobile device.

At act 2114, an annunciator or other alarm device (for example, ablinking lamp) activates to alert the vehicle operator that theremoval-event has occurred. In addition, where an annunciator is usedthe decibel level of the alarm can serve as motivation to the vehicleoperator (or any other occupant) to return the mobile device to thedocking station. Where act 2110 is included in the process 2100, thetime delay activation can be used to permit a temporary (for example,inadvertent) removal of the mobile device from the docking stationwithout either or both of recording an event (act 2112) or activating anannunciator (act 2114). In accordance with these embodiments, the delayis only temporary and the events in annunciator activation do occur ifthe mobile device is not returned to the docking station within apredetermined period of time.

At act 2116, a continued operation of the vehicle is permittedregardless of whether the mobile device is returned to the dockingstation. According to this embodiment, the continued operation can allowthe operator to complete an immediate trip.

At act 2118, the vehicle was shut down by the operator, for example, atthe end of their current trip. In accordance with further embodiments,the logging of an event at act 2112 places the system in a state thatprevents further vehicle operation once the vehicle is shut downfollowing the event. According to this embodiment, the system (forexample, the controller 1304) must receive an input in the form ofeither a temporary-use code or a clearing/acknowledgment by a systemadministrator of the event before the vehicle can be operated again.

Thus, at act 2120, the process 2000 continues when the operator tries torestart the vehicle and the system determines whether a temporaryauthorization code has been received, or alternatively, whether theevents has been cleared and/or acknowledged by an administrator. Wherethe required input or acknowledgment are not received the process 2000repeats act 2120. According to these embodiments, the operator is unableto start the vehicle unless act 2120 is successfully completed. In someembodiments, the operator can contact a system administrator to receivea one-time code that when entered into the onboard system, for example,via a keypad included in the docking station, allows the vehicle to berestarted and returned for a single trip.

Provided that act 2120 is successfully completed, the process 2000 movesto act 2122 where it is determined whether the mobile device is receivedin the docking station. In the illustrated embodiment, the act 2122 isrepeated and the vehicle cannot be started, even following a successfulcompletion of act 2120, unless the mobile device is also received in thedocking station. The process continues at act 2124 where the vehicle canbe started by the operator following a successful completion of acts2120 and 2122. According to one embodiment, act 2122 is not included andthe vehicle can be started at act 2124 following act 2120.

Variations of the process 2100 can include the addition of one or moreacts, the removal of one or more acts or a combination of the preceding.Further, the sequence of the acts can be modified in some embodiments.

Referring now to FIG. 22, a docking system 2200 for a mobile device 2204is illustrated in accordance with some embodiments. In the illustratedembodiment, the docking system includes a docking station 2202 toreceive the mobile device 2204. In general, the docking system 2200provides a receptacle located in the vehicle where thevehicle-operator's mobile device is placed to allow vehicle operation.According to some embodiments, the system 2200 is set up to prevent thevehicle from being started unless the operator's mobile device 2204 isreceived by the docking station 2202. In other embodiments, the system2200 allows the vehicle to be started without the operator's mobiledevice 2204 received by the docking station 2202 but prevents thevehicle from being placed in gear until the mobile device 2204 isreceived by the docking station 2202.

In one embodiment, the docking station 2202 includes a housing 2206 thatincludes a receptacle 2208. The docking station also includes a userinterface 2210. In the illustrated embodiment, the user interface 2210includes a keypad with a set of pushbuttons, for example, a keypadsimilar to the keypad of a telephone or a QWERTY keyboard. According toother embodiments, the docking station includes a display and the userinterface 2210 is presented in a graphical user interface rendered inthe display. According to these embodiments, the user interface 2210 isoperated via a touchscreen display and/or a mouse or trackball to guidea cursor for selecting icons presented in the display. In oneembodiment, a touch keypad is presented in the display. Where thedocking station 2202 includes a display, the display can include OLEDtechnology, LCD technology, light emitting polymer display technology orother display technology suitable for presenting information to a userin a visual format.

According to one embodiment, the user interface 2212 is attached to thehousing 2206 via a pivoting connection 2212 (for example, a hinge). Thiscan allow the vehicle operator to more easily access the user interfacewith the docking station 2202 mounted in the vehicle by providing arange of motion by which the vehicle operator can adjust the orientationof the display relative to the remainder of the docking station 2202.

Depending on the embodiment, the docking station 2202 can be mounted inthe vehicle using any of a variety of approaches. According to oneembodiment, the docking station 2202 includes mounting hardware 2214 toallow the docking station to be attached to a surface in the vehicleusing one or more fasteners, for example, mounted within arm's reach ofthe vehicle operator. According to another embodiment, the mountinghardware 2214 is attached to an adapter 2216 that allows the dockingstation 2202 to be attached to another mount 2218, for example, a RAMMount®. According to these embodiments, the manner in which the dockingstation 2202 is mounted in the vehicle can further increase the range ofmotion and adjustability of the docking station for the convenience ofthe vehicle operator.

According to some embodiments, the mobile device 2004 is housed in acase before being inserted in the receptacle 2208 while in otherembodiments a case is not employed. In still further embodiments, thedocking station 2002 may include a sleeve or adapter placed in thereceptacle 2208 to modify the dimensions for receipt of the mobiledevice 2004.

Referring now to FIG. 23A, a plan view of the docking station 2202 isillustrated from a side opposite the user interface. The illustratedembodiment includes the adapter 2216 attached to the housing 2206 usingfasteners to attach the adapter to the housing via the mounting hardware2214 illustrated in FIG. 22A. According to one embodiment, the mount2218 is attached to the adapter 2216 via fasteners 2220.

FIG. 23B illustrates a cross-sectional view of the docking station 2202.According to this embodiment, the user interface 2210 is attached to thehousing 2206 via the pivoting connection 2212 and the mount 2218 isattached to the housing 2206 via the adapter 2216 on a side opposite theuser interface 2210. In the illustrated embodiment, the mount 2218includes a ball 2222 for attachment to a second portion of the mount(not illustrated) to complete a ball and socket connection between themount 2218 and the second portion of the mount. In these embodiments,the ball and socket connection provides increased convenience to thevehicle operator because it provides a wide range of motion throughwhich the docking station 2202 can be moved.

The cross-sectional view also illustrates a first circuit board 2224, asecond circuit board 2226 and a mobile-device connector 2228 (forexample, a USB connector, a mini USB connector, an Apple® 30 pinconnector, a 10 pin Lightning® connector, etc.). According to oneembodiment, the first circuit board 2224 includes the controller and thememory, for example, the controller 1304 and the memory 1316,respectively, illustrated in FIG. 13. In the illustrated embodiment, thesecond circuit board 2226 provides the electrical connection for themobile-device connector 2228. Further, each of the user interface 2210and the second circuit board 2226 can be connected to the first circuitboard via electrical wiring, for example, via separate ribbon cables.Either or both of the first circuit board 2224 and the second circuitboard 2226 can be electrically connected to other elements of a system(for example, the system 1300). According to one embodiment, the firstcircuit board 2224 is electrically connected to various input and outputcircuits, for example: a remote speaker, indicating lamp or otherannunciator; the vehicle electronic control unit; vehicle ignition/startcircuitry; vehicle power; or other electrical/electronic I/O.

According to some embodiments, alignment hardware is located within thereceptacle 2208 to improve the ease with which the connection betweenthe mobile-device connector 2228 in the mobile device is completed.According to one embodiment, a guide (for example, a sloped surfaceextending upward from the base of the receptacle 2208) is located oneither side of the mobile-device connector 2228 to align themobile-device connector 2228 with a corresponding connector included inthe mobile device.

According to one embodiment, the bottom of the receptacle 2208 includesone or more drain tubes designed to remove any fluid that isaccidentally spilled into the receptacle 2208. The drain tubes can beconfigured to route any such fluid from the receptacle 2208 out a bottomsurface 2230 to avoid fluid contact with any of the electronics includedin the docking station 2202.

Although the docking station 2202 illustrated in FIG. 22 includes areceptacle, other embodiments can receive a mobile device in a mannerdifferent than that illustrated in FIG. 22. In one embodiment, thedocking station includes a faceplate and is constructed such that mobiledevice can only be received in the docking station in an orientation inwhich the hands-on user interface of the mobile-device is blocked fromaccess/view with the mobile device received by the docking station. Forexample, alignment features can be included in the docking station aspreviously described with reference to FIG. 18.

Further, although a mobile phone 2204 is illustrated in FIG. 22 thedocking station 2202 can be configured to receive other types of mobiledevices such as a tablet computer (for example, an iPad), mobile phoneor other portable computing device. According to these embodiments, thehands-on user interface is rendered inaccessible with the mobile devicereceived by the docking station.

The apparatus, system and method described herein can each be employedin all manner of vehicles where distracted vehicle-operation canotherwise be a problem. For example, the apparatus, systems and methodsdescribed herein can be used to facilitate safe operation of a publictransit vehicle including buses, trolleys, subways and trains. Where thepublic transit vehicle includes a drive vehicle for additional vehiclescoupled with it (for example, a locomotive), the operation of the drivevehicle can be controlled with the apparatus, system and methoddescribed herein. The apparatus, system and method described herein canalso be employed with passenger vehicles (public or privately owned) andcommercial vehicles including trucks and planes.

In certain embodiments, the devices, systems and methods describedherein may include, or be used with, at least one processor optionallyelectrically coupled to one or more memory units. In certain examples,the module may be a larger part of a computer system, e.g., part of theECU of the vehicle, whereas in other examples, the module may be a standalone module and include its own processor. The computer system may be,for example, a general-purpose computer such as those based on Unix,Intel PENTIUM-type processor, Motorola PowerPC, Sun UltraSPARC,Hewlett-Packard PA-RISC processors, or any other type of processor. Insome examples, the processor may be an inexpensive processor that may beprogrammable to receive inputs from an administrator to configure thesystem as desired. It should be appreciated that one or more of any typecomputer system may be used according to various embodiments of thetechnology. Further, the system may be located on a single computer ormay be distributed among a plurality of computers attached by acommunications network. A general-purpose computer system may beconfigured, for example, to perform any of the described functionsincluding but not limited to: vehicle override, override time out, speedlimiter, and the like. It should be appreciated that the system mayperform other functions, including network communication, and thetechnology is not limited to having any particular function or set offunctions. It is desirable that the system permit remote access to allowan administrator to configure the system on the fly.

For example, various aspects may be implemented as specialized softwareexecuting in a general-purpose computer system. The computer system mayinclude a processor connected to one or more memory units, such as adisk drive, memory, or other device for storing data. The memory unit istypically used for storing programs and data during operation of thedevice. Components of the computer system may be coupled by aninterconnection device, which may include one or more buses (e.g.,between components that are integrated within a same machine) and/or anetwork (e.g., between components that reside on separate discretemachines). The interconnection device provides for communications (e.g.,signals, data, instructions) to be exchanged between system componentsof the system. The interconnection device typically is electricallycoupled to the processor such that electrical signals may be provided tocontrol operation of the vehicle.

The computer system may also include one or more input devices, forexample, a keyboard, mouse, trackball, microphone, touch screen, touchpad, manual switch (e.g., override switch) and one or more outputdevices, for example, a printing device, display screen, speaker, etc.In addition, the computer system may contain one or more interfaces (notshown) that connect computer system 800 to a communication network inaddition or as an alternative to the interconnection device.

The storage system typically includes a computer readable and writeablenonvolatile recording medium in which signals are stored that define aprogram to be executed by the processor or information stored on or inthe medium to be processed by the program. For example, the SIM cardidentifiers, user-specified parameters, time out periods, overrideparameters and the like used in certain embodiments disclosed herein maybe stored on the medium. The medium may, for example, be a disk or flashmemory. Typically, in operation, the processor causes data to be readfrom the nonvolatile recording medium into another memory that allowsfor faster access to the information by the processor than does themedium. This memory is typically a volatile, random access memory suchas a dynamic random access memory (DRAM) or static memory (SRAM). It maybe located in the storage system or in memory system, for example. Theprocessor generally manipulates the data within the integrated circuitmemory and then copies the data to the medium after processing iscompleted. A variety of mechanisms are known for managing data movementbetween the medium and the integrated circuit memory element, and thetechnology is not limited thereto. The technology is also not limited toa particular memory system or storage system.

In certain examples, the computer system may also includespecially-programmed, special-purpose hardware, for example, anapplication-specific integrated circuit (ASIC). Aspects of thetechnology may be implemented in software, hardware or firmware, or anycombination thereof. Further, such methods, acts, systems, systemelements and components thereof may be implemented as part of thecomputer system described above or as an independent component that canbe added to the vehicle, e.g., either through software upload or byusing a separate module that is added to the vehicle's electricalsystem.

Although a computer system is described by way of example as one type ofcomputer system upon which various aspects of the technology may bepracticed, it should be appreciated that aspects are not limited tobeing implemented on any particular type of computer system. Variousaspects may be practiced on one or more computers having a differentarchitecture or components than that described herein. The computersystem may be a general-purpose computer system that is programmableusing a high-level computer programming language. The computer systemmay be also implemented using specially programmed, special purposehardware. In the computer system, the processor is typically acommercially available processor such as the well-known Pentium classprocessor available from the Intel Corporation. Many other processorsare available. Such a processor usually executes an operating systemwhich may be, for example, the Windows 95, Windows 98, Windows NT,Windows 2000 (Windows ME), Windows XP or Windows Vista operating systemsavailable from the Microsoft Corporation, MAC OS System X operatingsystem available from Apple Computer, the Solaris operating systemavailable from Sun Microsystems, or UNIX or Linux operating systemsavailable from various sources. Many other operating systems may beused, and in certain embodiments a simple set of commands orinstructions may function as the operating system.

In certain examples, the processor and operating system may togetherdefine a computer platform for which application programs in high-levelprogramming languages may be written. For example, the technologydescribed herein may be tunable or controllable by an administratorwhere the administrator can add vehicle specific functions based ontheir needs or desires. It should be understood that the technology isnot limited to a particular computer system platform, processor,operating system, or network. Also, it should be apparent to thoseskilled in the art, given the benefit of this disclosure, that thepresent technology is not limited to a specific programming language orcomputer system. Further, it should be appreciated that otherappropriate programming languages and other appropriate computer systemscould also be used.

In certain examples, the hardware or software can be configured toimplement cognitive architecture, neural networks or other suitableimplementations. For example, a remote operator database may be linkedto the system to permit operation of the vehicle by those usersspecified in the operator database. Such configuration provides foroperation of the vehicle by many different users as specified off-site.One or more portions of the computer system may be distributed acrossone or more computer systems coupled to a communications network. Thesecomputer systems also may be general-purpose computer systems. Forexample, various aspects may be distributed among one or more computersystems configured to provide a service (e.g., servers) to one or moreclient computers, or to perform an overall task as part of a distributedsystem. In some examples, the module in the vehicle may function as aclient computer and a remote server may be present at an administratorsite and can be configured to send commands to the client computer. Forexample, various aspects may be performed on a client-server ormulti-tier system that includes components distributed among one or moreserver systems that perform various functions according to variousembodiments. These components may be executable, intermediate (e.g., IL)or interpreted (e.g., Java) code which communicate over a communicationnetwork (e.g., the Internet) using a communication protocol (e.g.,TCP/IP), Bluetooth, etc. It should also be appreciated that thetechnology is not limited to executing on any particular system or groupof systems. Also, it should be appreciated that the technology is notlimited to any particular distributed architecture, network, orcommunication protocol.

In some examples, various embodiments may be programmed using anobject-oriented programming language, such as SmallTalk, Basic, Java,C++, Ada, or C# (C-Sharp). Other object-oriented programming languagesmay also be used. Alternatively, functional, scripting, and/or logicalprogramming languages may be used. Various configurations may beimplemented in a non-programmed environment (e.g., documents created inHTML, XML or other format that, when viewed in a window of a browserprogram, render aspects of a graphical-user interface (GUI) or performother functions). Certain configurations may be implemented asprogrammed or non-programmed elements, or any combination thereof.

When introducing elements of the examples disclosed herein, the articles“a,” “an,” “the” and “said” are intended to mean that there are one ormore of the elements. The terms “comprising,” “including” and “having”are intended to be open-ended and mean that there may be additionalelements other than the listed elements. It will be recognized by theperson of ordinary skill in the art, given the benefit of thisdisclosure, that various components of the examples can be interchangedor substituted with various components in other examples.

Although certain aspects, examples and embodiments have been describedabove, it will be recognized by the person of ordinary skill in the art,given the benefit of this disclosure, that additions, substitutions,modifications, and alterations of the disclosed illustrative aspects,examples and embodiments are possible.

What is claimed is:
 1. A system configured to control use of a mobile device in a vehicle, the mobile device comprising a hands-on user interface and a wireless communication interface, the system comprising: a docking station configured to receive the mobile device and to couple to the mobile device using a hardwired connection, wherein the hands-on interface is inaccessible with the mobile device received in the docking station and the wireless communication interface remains operational with the mobile device coupled to the docking station through the hardwired connection; and a controller configured to couple to the docking station and a vehicle-start system, the controller configured to allow operation of the vehicle with the mobile device coupled to the docking station via the hardwired connection and to prevent a vehicle start when the mobile device is not coupled to the docking station via the hardwired connection, wherein the controller is configured to permit, once the vehicle is started, a continued operation of the vehicle following removal of the mobile device from the docking station.
 2. The system of claim 1, wherein the controller is further configured to allow the vehicle to be started following receipt, from the mobile device via the hardwired connection, of information that uniquely identifies the mobile device.
 3. The system of claim 2, wherein the mobile device includes a mobile phone, and wherein the information includes at least one of a SIM number, an IMEI number and a USB serial number.
 4. The system of claim 1, wherein the controller includes a memory, and wherein the controller is configured to save a record in the memory in response to a removal of the mobile device from the docking station with the vehicle operating.
 5. The system of claim 4, wherein the system is configured to not permit a re-starting of the vehicle when the memory includes the record of the removal of the mobile device from the docking station with the vehicle operating.
 6. The system of claim 5, wherein, following the record of the removal of the mobile device from the docking station of an operating vehicle, the system is configured to permit re-starting out the vehicle following entry of a code associated with an authorization to operate the vehicle.
 7. The system of claim 6, wherein the docking station comprises a user interface, and wherein the user interface is configured for entry of the code.
 8. The system of claim 7, wherein the user interface comprises a keypad.
 9. The system of claim 1, further comprising at least one relay coupled to the controller, the controller configured to actuate the at least one relay to prevent the vehicle from starting if the mobile device is not coupled to the docking station via the hardwired connection.
 10. The system of claim 1, wherein the docking station includes at least one sensor coupled to the controller, the at least one sensor configured to detect if the mobile device is received by the docking station.
 11. The system of claim 1, further comprising an annunciator coupled to the controller, the controller configured to operate the annunciator to notify an operator of the vehicle when the mobile device is removed from the docking station with the vehicle operating.
 12. The system of claim 11, wherein the annunciator comprises an audible annunciator.
 13. The system of claim 1, wherein the docking station comprises the controller and a user interface.
 14. A method of controlling use of a mobile device in a vehicle, the vehicle comprising a docking station configured to receive the mobile device, the mobile device comprising a hands-on interface and a wireless communication interface, the method comprising: receiving the mobile device with the docking station via a hardwired connection, wherein the hands-on interface is inaccessible with the mobile device received by the docking station and the wireless communication interface remains operational with the mobile device received by the docking station; if the mobile device received by the docking station is an authorized mobile device: allowing the vehicle to start; and if the mobile device received by the docking station is an unauthorized mobile device; preventing the vehicle from starting; and permitting, once the vehicle is started, a continued operation of the vehicle following an uncoupling of the mobile device from the hardwired connection with the docking station.
 15. The method of claim 14, further comprising authenticating a mobile-device ID communicated from the mobile device to determine whether the mobile device coupled to the docking station is the authorized mobile device.
 16. The method of claim 15, further comprising authenticating the mobile-device ID using a USB serial number associated with the mobile device.
 17. The method of claim 14, further comprising saving a record of a removal of the mobile device from the docking station with the vehicle operating.
 18. The method of claim 17, further comprising preventing a re-starting of the vehicle when the record comprises an identification of the removal of the mobile device from the docking station with the vehicle operating.
 19. The method of claim 18, further comprising permitting the re-starting of the vehicle following entry of a code that permits operation of the vehicle.
 20. The method of claim 19, further comprising receiving the code via a user interface included in the docking station.
 21. The method of claim 14, further comprising determining whether the mobile device is received by the docking station using a sensor included in the docking station.
 22. The method of claim 14, further comprising determining, subsequent to the starting of the vehicle, whether the mobile device remains coupled to the docking station by monitoring a status of a USB connection of the mobile device and the docking station.
 23. The method of claim 22, wherein the act of determining includes an act of receiving an ID associated with the authorized mobile device.
 24. The method of claim 23, further comprising authenticating the mobile device by comparing the ID associated with the authorized mobile device with a mobile-device ID communicated from the mobile device coupled to the docking station.
 25. The method of claim 24, further comprising periodically polling the mobile device for the mobile-device ID to confirm that the mobile device remains in the docking station while the vehicle is operating.
 26. The method of claim 25, further comprising generating an audible alarm in the vehicle following a removal of the mobile device from the docking station while the vehicle is operating. 